-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is v1.2.0 compatible with Kubernetes 1.16? If not, can the project provide a compatibility matrix? #1939
Comments
Every ArgoRollout release supports the latest & latest-1 versions only. But you are correct, it is not mentioned anywhere in the docs and we will update them |
I think this is also a problem for ingress versions #1507 (there's a flag for it)
I'm not sure that's true as only 1.2.0 supports kubernetes 1.22 and above. And 1.1.0 was released when 1.22 was latest. |
So, I bumped into this just today. We're running K8S So what is the minimum version of K8S required in order to use argo-rollouts |
This issue is stale because it has been open 60 days with no activity. |
This issue is stale because it has been open 60 days with no activity. |
Closing this one since it has been solved by #2163 |
Summary
Previously, some of our clusters had Argo Rollouts v1.1.1 installed via helm charts located in the argo-helm repository. When we tried to upgrade to v1.2.0, we encountered the following error
I guess
x-kubernetes-map-type
was added in k8s 1.17. If Argo Rollouts is not compatible with k8s 1.16 clusters, it may be good to state this information somewhere? Maybe release notes if that is the case or a compatibility matrix for recent versions (like: https://github.com/open-telemetry/opentelemetry-operator#opentelemetry-operator-vs-kubernetes-vs-cert-manager)? Or with some sort of skip validation option can someone install it to a v1.16 cluster?Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: