Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(drain cleaner): considerations when using anti-affinity #9482

Merged
merged 2 commits into from
Dec 22, 2023
Merged

docs(drain cleaner): considerations when using anti-affinity #9482

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f0f76fc
docs(drain cleaner): considerations when using anti-affinity
PaulRMellor Dec 21, 2023
9747c4a
docs(review): edits to doc from comments by FV and JS
PaulRMellor Dec 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions documentation/modules/managing/proc-drain-cleaner-using.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@ The Cluster Operator performs rolling updates based on the annotation.

* You have xref:proc-drain-cleaner-deploying-{context}[deployed the Strimzi Drain Cleaner].

.Considerations when using anti-affinity configuration

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

. Drain a specified Kubernetes node hosting the Kafka broker or ZooKeeper pods.
Expand Down
Loading