Skip to content

Commit

Permalink
docs(review): edits to doc from comments by FV and JS
Browse files Browse the repository at this point in the history
Signed-off-by: prmellor <[email protected]>
  • Loading branch information
PaulRMellor committed Dec 22, 2023
1 parent f0f76fc commit 9747c4a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions documentation/modules/managing/proc-drain-cleaner-using.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ The Cluster Operator performs rolling updates based on the annotation.

.Considerations when using anti-affinity configuration

If using xref:assembly-scheduling-str[anti-affinity] with your Kafka or ZooKeeper pods, consider adding a spare worker node to your cluster or allowing pod rescheduling on the master node.
Including spare nodes ensures that your cluster has the capacity to reschedule pods, especially during node draining or temporary unavailability of other nodes.
When a worker node is drained, and anti-affinity rules restrict pod rescheduling on alternative nodes, spare nodes help prevent restarted pods from becoming unschedulable on other worker nodes. This mitigates the risk of the draining operation failing.
When using xref:assembly-scheduling-str[anti-affinity] with your Kafka or ZooKeeper pods, consider adding a spare worker node to your cluster.
Including spare nodes ensures that your cluster has the capacity to reschedule pods during node draining or temporary unavailability of other nodes.
When a worker node is drained, and anti-affinity rules restrict pod rescheduling on alternative nodes, spare nodes help prevent restarted pods from becoming unschedulable. This mitigates the risk of the draining operation failing.

.Procedure

Expand Down

0 comments on commit 9747c4a

Please sign in to comment.