Remove deprecated note on "Set up a High Availability etcd Cluster with kubeadm" page (#48120)
* Remove note from setup-ha-etcd-with-kubeadm.md * Remove note from setup-ha-etcd-with-kubeadm.md Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com> * Remove note from setup-ha-etcd-with-kubeadm.md Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com> --------- Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com>pull/48162/head
parent
513d4dfe82
commit
40419a5ef5
|
@ -8,13 +8,6 @@ weight: 70
|
|||
|
||||
<!-- 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 >}}
|
||||
|
||||
By default, kubeadm runs a local etcd instance on each control plane node.
|
||||
It is also possible to treat the etcd cluster as external and provision
|
||||
|
|
Loading…
Reference in New Issue