-
Notifications
You must be signed in to change notification settings - Fork 42k
CoreDNS should not tolerate master taints #70868
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
CoreDNS should not tolerate master taints #70868
Conversation
Otherwise users will be surprised when CoreDNS starts running on their masters, where kube-dns did not. Issue kubernetes#70851
|
/assign @chrisohaver @rajansandeep |
|
xref #54945 |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, MrHohn 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 |
rajansandeep
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.
/lgtm
|
/retest |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
Can we triage into milestone 1.13 - not sure who should make that call - @roberthbailey or @thockin ? I think there might actually be a case for only running on the master (as proposed in #54945), once we have the DNS node-local agent that @prameshj is working on in #70555. But the node-local agent needs time to bake before we make that decision, IMO. |
|
/milestone v1.13 |
|
/retest Review the full test history for this PR. Silence the bot with an |
Otherwise users will be surprised when CoreDNS starts running on their
masters, where kube-dns did not.
Issue #70851
/kind bug