kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #30264 from doughgle/patch-2 

Clarify why cordon all but 4 nodes.
This commit is contained in:
Kubernetes Prow Robot 2021-11-25 06:54:34 -08:00 committed by GitHub
parent 44a3025b52 b2035168a7
commit fe2b4047db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/en/docs/tutorials/stateful-application/zookeeper.md
View File

@ -894,8 +894,7 @@ Use this command to get the nodes in your cluster.
kubectl get nodes
```
Use [`kubectl cordon`](/docs/reference/generated/kubectl/kubectl-commands/#cordon) to
cordon all but four of the nodes in your cluster.
This tutorial assumes a cluster with at least four nodes. If the cluster has more than four, use [`kubectl cordon`](/docs/reference/generated/kubectl/kubectl-commands/#cordon) to cordon all but four nodes. Constraining to four nodes will ensure Kubernetes encounters affinity and PodDisruptionBudget constraints when scheduling zookeeper Pods in the following maintenance simulation.
```shell
kubectl cordon <node-name>