From 344aa1577970392dcde7bf3ac4ef99872b067f59 Mon Sep 17 00:00:00 2001 From: SataQiu Date: Sun, 28 Nov 2021 23:25:55 +0800 Subject: [PATCH] kubeadm: add instructions about rebalancing CoreDNS Pods after joining more nodes --- .../tools/kubeadm/create-cluster-kubeadm.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md index 4ca61bfc8c..9d7b717594 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md @@ -383,6 +383,12 @@ Run 'kubectl get nodes' on control-plane to see this machine join. A few seconds later, you should notice this node in the output from `kubectl get nodes` when run on the control-plane node. +{{< note >}} +As the cluster nodes are usually initialized sequentially, the CoreDNS Pods are likely to all run +on the first control-plane node. To provide higher availability, please rebalance the CoreDNS Pods +with `kubectl -n kube-system rollout restart deployment coredns` after at least one new node is joined. +{{< /note >}} + ### (Optional) Controlling your cluster from machines other than the control-plane node In order to get a kubectl on some other computer (e.g. laptop) to talk to your