whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

kubeadm: clarify the usage of kubeadm commands in our external etcd guide (#17541)

Browse Source
This commit is contained in:
SataQiu
2019-11-13 16:43:11 +08:00
committed by Kubernetes Prow Robot
parent 75c0e190c4
commit c1c108f044
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
+8
View File
@@ -8,6 +8,14 @@ weight: 70
{{% capture overview %}} {{% capture overview %}}
{{< note >}}
While kubeadm is being used as the management tool for external etcd nodes
in this guide, please note that kubeadm does not plan to support certificate rotation
or upgrades for such nodes. The long term plan is to empower the tool
[etcdadm](https://github.com/kubernetes-sigs/etcdadm) to manage these
aspects.
{{< /note >}}
Kubeadm defaults to running a single member etcd cluster in a static pod managed Kubeadm defaults to running a single member etcd cluster in a static pod managed
by the kubelet on the control plane node. This is not a high availability setup by the kubelet on the control plane node. This is not a high availability setup
as the etcd cluster contains only one member and cannot sustain any members as the etcd cluster contains only one member and cannot sustain any members