Update terminology to be racially neutral

[scottstout]

This is a Feature Request

What would you like to be added
Terminology should be updated to be more racially neutral.
whitelist --> allowlist
blacklist --> denylist

In many cases these words can be avoided all together. For example if the sentence is "the following IP addresses should be whitelisted" you can change it to "the following IP addresses should be allowed". This is probably more clear language.

master/slave --> director/worker?

Why is this needed
Create a more inclusive environment in tech.
Make the world slightly better.

Comments
There is a similar feature request in kubernetes/kubernetes here:
kubernetes/kubernetes#90277
I have created a PR to fix the issues in the docs/website here:
#21591

[rlenferink]

Didn’t we already change master to control plane some time ago @sftim ?

[scottstout]

Some examples (some are possibly just docs changes while some are API/service changes):
https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively

https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/#scaling-the-number-of-slaves

kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap
kubectl --docker-env-metadata-whitelist string

scheduler.alpha.kubernetes.io/tolerationsWhitelist
https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#podtolerationrestriction

More generally:
https://kubernetes.io/docs/search/?q=whitelist
https://kubernetes.io/docs/search/?q=slave

[zacharysarah]

@scottstout Thanks for opening this!

Partial fix (allow list/deny list) in #21591

[jboeshart]

Adding the following to the list as well. Updating this could help enable downstream services (AKS) to adopt more inclusive terminology without having to deviate from the source project terminology.

https://kubernetes.io/docs/concepts/#kubernetes-master

[sftim]

Relates to #21749 and to the new Naming working group.

[celestehorgan]

/wg naming

[devurandom]

These two pages also make reference to "master" VMs or machines:

• https://kubernetes.io/docs/concepts/overview/components/
• https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/

[neolit123]

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/

a PR to replace:

"for the masters"

with:

"for the control-planes Nodes"

is welcome.

[devurandom]

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/

a PR [...] is welcome.

Thanks: #23847

[sftim]

/triage accepted

[justaugustus]

/assign @celestehorgan

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[celestehorgan]

/remove lifecycle-stale

[celestehorgan]

/remove-lifecycle stale

[celestehorgan]

@kubernetes/wg-naming-leads – we've already done work around this for whitelist/blacklist but our recommendation on master/slave needs some work. Regardless I'd like to close this issue because I think it's too broad.

[marians]

Has a decision been made yet regarding the naming of the feature "High-Availability Kubernetes Masters"? See https://kubernetes.io/docs/tasks/administer-cluster/highly-available-master/

If yes, we'd like to apply the new term to our documentation and communication.

[marians]

@kubernetes/wg-naming-leads @celestehorgan Is there any progress on this?

I'd like to suggest some options for renaming "High-Availability Kubernetes Masters":

• (a) High-availability control plane
• (b) Highly available control plane

[sftim]

https://kubernetes.io/docs/tasks/administer-cluster/highly-available-control-plane/ now replaces https://kubernetes.io/docs/tasks/administer-cluster/highly-available-master/

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[scottstout]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[scottstout]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.