-
Notifications
You must be signed in to change notification settings - Fork 867
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
Compatibility issue #2718
Comments
It should be compatible, I will try to upgrade k8s deps for 1.5 as well. |
when we can expect 1.5 stable version. |
I believe that compatibility between Argo Rollouts and Kubernetes is not well explained in the documentation. It is really hard to know, at one point in time, which version Argo Rollouts 1.4.1 (as an example) is compatible with. I don't think the N, N-1 guidelines are easy to follow since it is hard to cross-check versions of both Argo Rollouts and Kubernetes. One way to make it more clear is to clearly state the compatibility target on the release notes. |
Yea agree, just for information what is currently being tested https://github.com/argoproj/argo-rollouts/blob/master/.github/workflows/e2e.yaml#L40-L44 and you could go look at different branches as well and see what e2e test where ran then. Docs could probably be updated as well. Just to not rollouts does not interact with k8s all that much as far as breaking versions due to k8s upgrades so it will generally work on a wide range of versions some features of the pod spec might be missing depending on what client lib is pulled into rollouts however. |
This issue is stale because it has been open 60 days with no activity. |
Resolves argoproj#2718 Signed-off-by: Andy Chen <[email protected]>
Resolves #2718 Signed-off-by: Andy Chen <[email protected]>
is v1.5.0-rc1 release is compatible with EKS 1.22.17?
if not, which version can be used for supporting EKS 1.22 and 1.23 since we are observing vulnerability issue related k8s version.
The text was updated successfully, but these errors were encountered: