From b2035168a7a936a4e69c083741e01b4f048d286f Mon Sep 17 00:00:00 2001 From: Douglas Hellinger Date: Wed, 27 Oct 2021 15:58:55 +0800 Subject: [PATCH] Clarify why cordon all but 4 nodes. --- content/en/docs/tutorials/stateful-application/zookeeper.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/tutorials/stateful-application/zookeeper.md b/content/en/docs/tutorials/stateful-application/zookeeper.md index 3ed1cd454b..96c2ebcd0f 100644 --- a/content/en/docs/tutorials/stateful-application/zookeeper.md +++ b/content/en/docs/tutorials/stateful-application/zookeeper.md @@ -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