-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Replace words 'master', 'slave' with something else #30284
Comments
@jihoon-seo going throught the docs I feel the same we should avoid using these words and should look for alternatives also I wondering if the label |
Thank you for this issue, Jihoon. A quick search for "master" alone shows 72 results across 39 files. We should review and fix where applicable.
/sig docs |
I think |
It depends on the context too. Where applicable, replace Kubernetes master with control plane. Primary/secondary is a good substitute for controllers with that master/slave terminology. Worth doing multiple smaller PRs for this so that instances can be discussed and reviewed. |
Thank you all for your comments!
This label was added because I used the "Feature Request" issue template. /remove-kind feature |
This issue is a duplicate of issue #21621. |
/close |
/remove-triage accepted |
@jihoon-seo: This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a Feature Request
What would you like to be enhanced
Replace words 'master', 'slave' with something else.
For example, in https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ ,
the terms 'redis-leader' and 'redis-follower' are used.
Why is this needed
It seems good to avoid to use the words like 'master' and 'slave'.
Comments
/language en
The text was updated successfully, but these errors were encountered: