-
Notifications
You must be signed in to change notification settings - Fork 690
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
Manifest not compatible with Kubernetes 1.19+ #454
Comments
It would be nice to have a flag or something to specify what version to use, if you wish to change it from default. The default could probably be whatever is compatible with current version and prior 2 versions. |
and k8s 1.18 is End-Of-Life in 3 months.. So we'd like to be able to upgrade (with sealed secrets working) to 1.20 soon :) |
possibly this issue has not been updated with the latest fixes. does any of the following open issues block an upgrade to 1.20?
|
so in latest v0.14.0 - CRD has been fixed to work with 1.20.. (would be very good :) |
sorry I don't understand what you mean here (my brain is not 100% lately). Is the latest release (v0.14.1) working for you on 1.20 or not? |
I added k8s v1.20.1 to the integration test matrix in #533 |
moving the other non blocking cleanups into #534 |
In parallel with #269 a lot of the resources still has v1beta attached to it's apiVersion of it's version 0.12.5.
The text was updated successfully, but these errors were encountered: