-
Notifications
You must be signed in to change notification settings - Fork 242
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
CCM/CSI migration support for clusters with static worker nodes #1544
Conversation
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.
Consider yourself reviewed!
Signed-off-by: Marko Mudrinić <[email protected]>
Signed-off-by: Marko Mudrinić <[email protected]>
7f9dff6
to
ff78b0e
Compare
/hold |
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.
/approve
LGTM label has been added. Git tree hash: 8b748575b0e77574c63d9d4a76e2e7065d9e0768
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xmudrii, xrstf 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 |
/retest |
What this PR does / why we need it:
This PR introduces CCM/CSI migration support for clusters with the static worker nodes. As described in #1495,
kubeadm
cannot be used to handle updating kubelet configuration and flags. This is becausekubeadm init
(used for control plane nodes) works differently thankubeadm join
(used for static worker nodes).To mitigate that, we manually update the required files, which we already do for Docker to containerd migration.
The workflow is:
/var/lib/kubelet/config.yaml
)kubeadm-flags.env
file (/var/lib/kubelet/kubeadm-flags.env
)--cloud-provider=external
and remove the--cloud-config
flagkubeadm-flags.env
This PR has been already tested on an OpenStack cluster.
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 #1495
Fixes #1450
Does this PR introduce a user-facing change?: