Skip to content

Commit b203516

Browse files
authored
Clarify why cordon all but 4 nodes.
1 parent 6490aaf commit b203516

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

content/en/docs/tutorials/stateful-application/zookeeper.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -894,8 +894,7 @@ Use this command to get the nodes in your cluster.
894894
kubectl get nodes
895895
```
896896

897-
Use [`kubectl cordon`](/docs/reference/generated/kubectl/kubectl-commands/#cordon) to
898-
cordon all but four of the nodes in your cluster.
897+
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.
899898

900899
```shell
901900
kubectl cordon <node-name>

0 commit comments

Comments
 (0)