-
Notifications
You must be signed in to change notification settings - Fork 39.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
NODE_TAINTS in gce startup scripts #47632
NODE_TAINTS in gce startup scripts #47632
Conversation
Is this required for 1.7 release or not? There is no issue associating with this pr, and no review. |
This small fix is needed to have a reasonable support for taints in node pools in GKE. It has an issue in our internal bug tracking system ... since November. @gmarek did an initial review today. I need to run one more check and we should be good to go. |
c806c57
to
9143569
Compare
/lgtm |
/approve no-issue |
Do you need to do this with GCI as well? |
@mikedanese I modified both for consistency. |
/approve |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gmarek, mikedanese, mwielgus Associated issue requirement bypassed by: mikedanese The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test pull-kubernetes-e2e-gce-etcd3 |
/retest |
Automatic merge from submit-queue (batch tested with PRs 45268, 47573, 47632, 47818) |
Automatic merge from submit-queue (batch tested with PRs 45268, 47573, 47632, 47818) NODE_TAINTS in gce startup scripts Currently there is now way to pass a list of taints that should be added on node registration (at least not in gce or other saltbased deployment). This PR adds necessary plumbing to pass the taints from user or instance group template to kubelet startup flags. ```release-note Taints support in gce/salt startup scripts. ``` The PR was manually tested. ``` NODE_TAINTS: 'dedicated=ml:NoSchedule' ``` in kube-env results in ``` spec: [...] taints: - effect: NoSchedule key: dedicated timeAdded: null value: ml ``` cc: @davidopp @gmarek @dchen1107 @MaciekPytel
Currently there is now way to pass a list of taints that should be added on node registration (at least not in gce or other saltbased deployment). This PR adds necessary plumbing to pass the taints from user or instance group template to kubelet startup flags.
The PR was manually tested.
in kube-env results in
cc: @davidopp @gmarek @dchen1107 @MaciekPytel