Merge pull request #30657 from SataQiu/fix-kubeadm-20211128

kubeadm: add instructions about rebalancing CoreDNS Pods after joining more nodes
pull/30705/head^2
Kubernetes Prow Robot 2021-12-01 04:21:14 -08:00 committed by GitHub
commit 819d7c8289
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions

View File

@ -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