-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Restart kube-proxy using kubeadm & add bootstrapper.WaitCluster #4276
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tstromberg 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 |
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.
Looks good to me.
The logic in
updateKubeProxyConfigMap
was broken: there is no need for kube-proxy to be online to update the config map for it. This PR lets kubeadm handle the kube-proxy restart instead, which apparently does things correctly on newer Kubernetes versions.Full credit goes to @liubog2008 who proposed a similar approach in #4014
NOTE: This PR also moves
validateCluster
tobootstrapper.WaitCluster
to allow for more a more tuned implementation.This fixes #3843