-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
Automated cherry pick of #65931: kubeadm: run kube-proxy on non-master tainted nodes #66043
Automated cherry pick of #65931: kubeadm: run kube-proxy on non-master tainted nodes #66043
Conversation
kube-proxy should be able to run on all nodes, independent on the taint of such nodes. This restriction was previously removed in bb28449 but then was brought back in d194926. Also, annotate with: scheduler.alpha.kubernetes.io/critical-pod: "" and add a class in the template spec: priorityClassName: system-node-critical
@timothysc @foxish our "cherry-tracking" list: |
@neolit123, can someone else eyeball this change and LGTM? |
nvm, saw that the pull is identical to the one that landed in master. |
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
Great, thanks all!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: foxish, luxas, 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 |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #65931 on release-1.11.
#65931: kubeadm: run kube-proxy on non-master tainted nodes