-
Notifications
You must be signed in to change notification settings - Fork 104
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
Bump direct dependencies to their latest releases #1685
Conversation
This changes the Kubernetes client API to 0.19.1. Furthermore, 'controller-tools' has been updated to a version that generates V1 CRDs. Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
I don't think we can drop support for the v1beta1 today. See for example this recent commit. |
Yes, switching to V1 CRDs would drop support for Kubernetes < 1.16 which would be in line with the proposed API version policy. |
Updating |
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Not all tooling is able to handle v1 CRDs yet, let's keep generating v1beta1 CRDs. Signed-off-by: Jan Schlicht <jan@d2iq.com>
I'll keep the CRDs at |
This reverts commit faece87. Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
Signed-off-by: Jan Schlicht <jan@d2iq.com>
What this PR does / why we need it:
This changes the Kubernetes client API to 0.19.2.
Furthermore,
controller-tools
has been updated. This version creates V1 CRDs by default, but its configuration has been changed to still create v1beta1 CRDs, as some clusters might have components that don't support V1 CRDs yet.Go 1.15 is used for builds.