From c1c108f044c00a2adc7073ef112490f13f6f0f09 Mon Sep 17 00:00:00 2001
From: SataQiu <1527062125@qq.com>
Date: Wed, 13 Nov 2019 16:43:11 +0800
Subject: [PATCH] kubeadm: clarify the usage of kubeadm commands in our
 external etcd guide (#17541)

---
 .../tools/kubeadm/setup-ha-etcd-with-kubeadm.md           | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
index 24adbbea628..b1f7f6bb801 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
+++ b/content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
@@ -8,6 +8,14 @@ weight: 70
 
 {{% 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
 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