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

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

Browse Source 
kubeadm: add instructions about rebalancing CoreDNS Pods after joining more nodes
This commit is contained in:
Kubernetes Prow Robot
2021-12-01 04:21:14 -08:00
committed by GitHub
parent be94f3ff50 344aa15779
commit 819d7c8289
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
+6
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