-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 Drop caBundle from CRDs to support Kubernetes 1.31 #10972
🐛 Drop caBundle from CRDs to support Kubernetes 1.31 #10972
Conversation
1320244
to
529dc2b
Compare
/cherry-pick release-1.8 |
/cherry-pick release-1.7 |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.7 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cherry-pick release-1.6 |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.6 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: Stefan Büringer [email protected]
529dc2b
to
ed83b13
Compare
/test ? |
@sbueringer: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/hold
drop hold if needed pls
LGTM label has been added. Git tree hash: af2eb9493e76557aff9d85ccb6eb495959456d86
|
/kind cleanup |
Thx! I'll keep the hold until tomorrow. Want to take a look at the results from #10970 |
Test failed on Christian's PR: #10970 (comment) I"ll now add dropping the caBundle to his PR to check if it fixes it |
/test pull-cluster-api-e2e-main |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi, neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
@sbueringer: new pull request created: #10976 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@sbueringer: #10972 failed to apply on top of branch "release-1.7":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@sbueringer: #10972 failed to apply on top of branch "release-1.6":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
See kubernetes-sigs/cluster-api#10972 Signed-off-by: Andrey Smirnov <[email protected]>
Kubernetes 1.31 will no longer allow the caBundle field to continuously reconcile to an invalid value. We'll fix this by leaving it blank. See kubernetes-sigs/cluster-api#10972 for more details. Signed-off-by: Nolan Brubaker <[email protected]>
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
Starting with Kubernetes 1.31 it won't be possible anymore to continuously apply CRDs that are setting caBundle to an invalid value (in our case
Cg==
). The solution is to simply drop the caBundle field (it was never actually required by kube-apiserver).For more details see: https://kubernetes.slack.com/archives/C0EG7JC6T/p1722441161968339
Let me know if you have any questions.
Going to backport this into all supported releases. It's never great to set the caBundle to an invalid value, even before Kubernetes 1.31
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #