-
Notifications
You must be signed in to change notification settings - Fork 42k
kubeadm: Fix node join taints #69846
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
kubeadm: Fix node join taints #69846
Conversation
|
/kind bug |
|
/test pull-kubernetes-e2e-kops-aws |
|
@andrewrynhard thanks for catching this. this is part of the 1.12.x release. should we backport? |
fabriziopandini
left a comment
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.
@andrewrynhard Thanks for this PR!
Only one minor nit and then lgtm for me
cmd/kubeadm/app/cmd/join.go
Outdated
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.
I think that the registerTaintsUsingFlags parameter should be set to true only in case cfg.ControlPlane == false, otherwise we are setting taints twice (here and afterwards when calling MarkMaster)
7a191c1 to
cf29093
Compare
cmd/kubeadm/app/cmd/join.go
Outdated
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.
@fabriziopandini !j.cfg.ControlPlane should address your concern.
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.
You are right, but I'm a little bit concerned that the reason behind that little ! will get lost soon.
What do you think about setting a new variable registerTaintsUsingFlags and adding a comment explaing why we that this is not required when the joining node should host a new control plane instance because taints will be applied afterwards by MarkMaster?
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.
Agree. Will push that up.
We probably should IMHO. |
cf29093 to
197fd02
Compare
|
@fabriziopandini Look better now? |
fabriziopandini
left a comment
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.
@andrewrynhard many many thanks for being so patient with me 😉
/approve
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewrynhard, fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR fixes a bug introduced in 8af751f, that prevents node taints from being applied that are specified in the
JoinConfiguration.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Special notes for your reviewer:
Release note:
/cc @fabriziopandini