Add support for affinity to allow spreading of kuberhealthy pods acro… #909
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
|
@joshulyne @integrii can you please review the PR ? Thanks! |
|
thanks @AshutoshNirkhe ! |
|
@AshutoshNirkhe thanks so much for contributing this! definitely something we needed! 👍 |
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.
Currently there isn't support for specifying the affinity/podAntiAffinity for Kuberhealthy pods. We noticed it when our Kuberhealthy pods in production env were running on the same node :)
kuberhealthy-5ccb966f45-5nngq 1/1 Running 0 2d7h 10.39.0.209 aks-xxxxx-15091357-vmss000002
kuberhealthy-5ccb966f45-pjpg8 1/1 Running 0 2d7h 10.39.0.190 aks-xxxxx-15091357-vmss000002
This PR will help you specify/apply those settings optionally to allow spreading of Kuberhealthy pods across nodes.