-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Ark v0.9.0 not compatible with pre-1.8 clusters #660
Comments
How important is the use case of folks using Ark to upgrade from an older version of K8s to a more modern one? Might this (and its ilk) be a key enabler of that use case? |
In this particular case the user upgraded their cluster and all's good. |
It's a use case we've suggested. However, we haven't yet made a firm decision on what our support window is. We'll definitely need a solid story on our k8s version window for 1.0. |
FYI we got a second user report of the same issue today. I'm inclined to just address this one for now, release an 0.9.1, and kick the can down the road on defining our compatibility matrix, i.e. still plan to do it for 1.0. Any objections? |
SGTM. Is your plan to try multiple api versions? |
xref #596 |
I had the same issue w/ a 1.7.2 cluster, and was able to use Ark 0.8.3 client/server to resolve. |
Thanks @metadave for the info. We'll also be releasing v0.9.1 shortly, which will bring back 1.7.x compatibility. |
A user reported that Ark was crashing on a 1.7.x cluster. It looks like the proximate cause for that is that the new backup item action that backs up cluster roles and role bindings related to a service account is using the
rbac.authorization.k8s.io/v1
API group/version, which doesn't exist pre-1.8 when RBAC went GA.It's possible there are other issues too; we haven't tested with 1.7 clusters.
Need to decide what our level of support should be for older versions of Kube going forward, and decide if we want to try to fix this specific issue.
cc @heptio/bluesteelsquad @rosskukulinski
The text was updated successfully, but these errors were encountered: