Skip to content
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-role.kubernetes.io/master -> node-role.kubernetes.io/control-plane #104

Closed
rdxmb opened this issue Apr 22, 2021 · 7 comments
Closed
Labels

Comments

@rdxmb
Copy link
Contributor

rdxmb commented Apr 22, 2021

Please adapt your tooling built on top of kubeadm to use the "node-role.kubernetes.io/control-plane" label.
The taint applied to control-plane nodes "node-role.kubernetes.io/master:NoSchedule" is now deprecated and will be removed in a future release after a GA deprecation period.
Apply toleration for a new, future taint "node-role.kubernetes.io/control-plane:NoSchedule" to the kubeadm CoreDNS / kube-dns managed manifests. Note that this taint is not yet applied to kubeadm control-plane nodes.

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md#no-really-you-must-read-this-before-you-upgrade

@geerlingguy
Copy link
Owner

What is this in relation to?

@rdxmb
Copy link
Contributor Author

rdxmb commented Apr 23, 2021

@rdxmb
Copy link
Contributor Author

rdxmb commented Apr 23, 2021

# kubectl get nodes eins -o yaml | grep -1 NoSchedule
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/control-plane

kubeadm version: v1.20.6

@geerlingguy
Copy link
Owner

@rdxmb - Ah, thanks!

@geerlingguy
Copy link
Owner

@rdxmb - Just merged the other major PR (config change)—would you like to take a stab at cleaning this up now?

@rdxmb
Copy link
Contributor Author

rdxmb commented May 7, 2021

hm,

  1. whats the goal here? Use both of the labels? Or only one of them?
  2. What about the comment in https://github.com/geerlingguy/ansible-role-kubernetes/blob/master/tasks/master-setup.yml#L79 We should fix this in one step.

@geerlingguy
Copy link
Owner

See: #126 — this will be a breaking change in the next major release of the role.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants