Merge pull request #23528 from yeldiRium/patch-1
Clarify kubelet service configuration
This commit is contained in:
+1
-1
@@ -51,6 +51,7 @@ this example.
|
|||||||
|
|
||||||
1. Configure the kubelet to be a service manager for etcd.
|
1. Configure the kubelet to be a service manager for etcd.
|
||||||
|
|
||||||
|
{{< note >}}You must do this on every host where etcd should be running.{{< /note >}}
|
||||||
Since etcd was created first, you must override the service priority by creating a new unit file
|
Since etcd was created first, you must override the service priority by creating a new unit file
|
||||||
that has higher precedence than the kubeadm-provided kubelet unit file.
|
that has higher precedence than the kubeadm-provided kubelet unit file.
|
||||||
|
|
||||||
@@ -270,4 +271,3 @@ Once you have a working 3 member etcd cluster, you can continue setting up a
|
|||||||
highly available control plane using the [external etcd method with
|
highly available control plane using the [external etcd method with
|
||||||
kubeadm](/docs/setup/production-environment/tools/kubeadm/high-availability/).
|
kubeadm](/docs/setup/production-environment/tools/kubeadm/high-availability/).
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user