docs(drain cleaner): considerations when using anti-affinity #9482
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: prmellor <pmellor@redhat.com>
fvaleri
approved these changes
Dec 21, 2023
scholzj
reviewed
Dec 21, 2023
Signed-off-by: prmellor <pmellor@redhat.com>
scholzj
approved these changes
Dec 22, 2023
ppatierno
approved these changes
Dec 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation
Updates the procedure for using the Drain Cleaner to include some general considerations when using anti-affinity on nodes.
Suggests using a spare worker node in case anti-affinity restrictions result in a pod being unschedulable and drain cleaner operation failing.
Checklist
Please go through this checklist and make sure all applicable tasks have been done