Skip to content

Commit ce9f2b4

Browse files
committed
kudeadm: Replace "master" with "control plane node"
This replaces the word "master" with "control plane node" in order to use more inclusive language. Also uses consistent wording / spelling in this context. References: kubernetes#21621 Suggested-by: Lubomir I. Ivanov <[email protected]>
1 parent e7e99cc commit ce9f2b4

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ LoadBalancer, or with dynamic PersistentVolumes.
3636
For both methods you need this infrastructure:
3737

3838
- Three machines that meet [kubeadm's minimum requirements](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#before-you-begin) for
39-
the masters
39+
the control plane nodes
4040
- Three machines that meet [kubeadm's minimum
4141
requirements](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#before-you-begin) for the workers
4242
- Full network connectivity between all machines in the cluster (public or
@@ -109,8 +109,8 @@ option. Your cluster requirements may need a different configuration.
109109
- The `--control-plane-endpoint` flag should be set to the address or DNS and port of the load balancer.
110110

111111
- The `--upload-certs` flag is used to upload the certificates that should be shared
112-
across all the control-plane instances to the cluster. If instead, you prefer to copy certs across
113-
control-plane nodes manually or using automation tools, please remove this flag and refer to [Manual
112+
across all the control plane instances to the cluster. If instead, you prefer to copy certs across
113+
control plane nodes manually or using automation tools, please remove this flag and refer to [Manual
114114
certificate distribution](#manual-certs) section below.
115115

116116
{{< note >}}
@@ -185,7 +185,7 @@ option. Your cluster requirements may need a different configuration.
185185
### Steps for the rest of the control plane nodes
186186

187187
{{< note >}}
188-
Since kubeadm version 1.15 you can join multiple control-plane nodes in parallel.
188+
Since kubeadm version 1.15 you can join multiple control plane nodes in parallel.
189189
Prior to this version, you must join new control plane nodes sequentially, only after
190190
the first node has finished initializing.
191191
{{< /note >}}
@@ -224,7 +224,7 @@ in the kubeadm config file.
224224
scp /etc/kubernetes/pki/apiserver-etcd-client.key "${CONTROL_PLANE}":
225225
```
226226

227-
- Replace the value of `CONTROL_PLANE` with the `user@host` of the first control plane machine.
227+
- Replace the value of `CONTROL_PLANE` with the `user@host` of the first control plane node.
228228

229229
### Set up the first control plane node
230230

@@ -352,7 +352,7 @@ SSH is required if you want to control all nodes from a single machine.
352352

353353
{{< caution >}}
354354
Copy only the certificates in the above list. kubeadm will take care of generating the rest of the certificates
355-
with the required SANs for the joining control-plane instances. If you copy all the certificates by mistake,
355+
with the required SANs for the joining control plane instances. If you copy all the certificates by mistake,
356356
the creation of additional nodes could fail due to a lack of required SANs.
357357
{{< /caution >}}
358358

0 commit comments

Comments
 (0)