倉庫指標
- Star
- (10,380 star)
- PR 合併指標
- (平均合併 25天) (30 天內合併 26 個 PR)
描述
What would you like to be added
a few years back the Kubernetes projected created a working group called "WG naming" backed by CNCF members which established that words like "master" are offensive in Kubernetes. the whole documentation at k8s.io. was revamped, a number areas of kubernetes/kubernetes were changed, kubeadm and other SIG Cluster Lifecycle subprojects changed too. there was a kubeadm master -> control plane taint migration if you recall.
as much as i like kubepray, it seems that often it ends up on a bit of an island, where it seems isolated from what's going on in the top level SIG and the K8s ecosystem. i was recently pinged on this issue https://github.com/kubernetes-sigs/kubespray/issues/11350 where i saw kubespray logs such as "Upgrade first master...".
https://github.com/search?q=repo%3Akubernetes-sigs%2Fkubespray+master&type=code
kubespray should stop using the wording "master" and you can execute on this action in a few steps:
- user facing non breaking changes such as log lines and documentation
- user facing breaking changes with deprecation periods and careful planning
- documenting impossible to change areas
please let me know if you have any questions.
/priority important-longterm
Why is this needed
compliance with the rest of the Kubernetes project