-
Notifications
You must be signed in to change notification settings - Fork 715
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
kinder: add handling of the new/old kubelet-config map #2654
kinder: add handling of the new/old kubelet-config map #2654
Conversation
With UnversionedKubeletConfigMap going Beta in 1.24 and enabled by default, we want to match what kubeadm is doing: - look of the new name of CM - if that fails fallback to the old CM name leave a TODO to remove this extra handling once 1.24 goes out of support. This would mean that all tested versions of kubeadm only have UnversionedKubeletConfigMap=true and the new CM name.
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
since this is only used by node up-gradation.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, pacoxu 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 |
let's merge this to let it run in CI. |
With UnversionedKubeletConfigMap going Beta in 1.24
and enabled by default, we want to match what kubeadm is doing:
leave a TODO to remove this extra handling once 1.24
goes out of support. This would mean that all tested
versions of kubeadm only have UnversionedKubeletConfigMap=true
and the new CM name.
xref #1582
xref kubernetes/kubernetes#108027
(does not depend strictly on the this PR)
NOTE: i'm not touching the only e2e test workflow for this because it already excercises the case for upgrading from a state with old names -> new names.
https://github.com/kubernetes/kubeadm/blob/main/kinder/ci/workflows/unversioned-kubelet-cm-tasks.yaml#L113-L125
we can technically add a new workflow with the FG turned off and tested during init, but i don't think that is necessary.