Open jessesuen opened 3 years ago
I do like this idea, but I feel that a compatibility matrix would belong more in the domain of the ecosystem's project.
Maybe the matrix should be maintained in each project separately at a given URL, and we link to it from Argo CD docs?
I wonder if we should introduce a "certify with the upcoming release of ArgoCD" program ?
Participating projects commit to releasing a tested version of the project with ArgoCD 2.1 for example.
The ecosystem projects ship a release simultaneous to the ArgoCD release - have a lightweight "certification" process.
The ecosystem projects send a PR to the relevant section of the ArgoCD docs specifying the version of the project compatible with the specific version of ArgoCD.
This ensures the following:
Hi @jessesuen
I would like to know how this issue is going on. Especially, due to our k8s cluster version upgrade task, I really need a k8s compatibility matrix table.
Regards, Jay Lee
Hi @jay-lee-otsk,
Especially, due to our k8s cluster version upgrade task, I really need a k8s compatibility matrix table.
If you are requesting information on compatibility between Argo CD and Kubernetes versions, our official stance is as follows:
ICYMI, there's a section for "ecosystem projects" in this list: https://github.com/terrytangyuan/awesome-argo#ecosystem-projects
Hi @jannfis cc @terrytangyuan
Noted with thanks. It was very helpful. I suggest this information be included in README.md shown on the front page. So that everyone could understand this community's official guidance.
Summary
We have several ecosystem argoproj-labs projects which integrate well with Argo CD and assume (or were only tested with) specific versions of Argo CD. These include:
We should improve our documentation to