Add topologyspreadconstraint to deploy pods in sts cross different az evenly #526
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
… evenly Signed-off-by: Wang, Shu <[email protected]>
|
Closing and reopening to trigger a new GitHub Actions workflow run after 6b31946 |
lhotari
approved these changes
Sep 27, 2024
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.
Fixes #521
Motivation
I see broker sts doesn't support topology constraint configuration. That means 2 pods in the sts may possible depoyed to on az in kubernetes cluster.
Reference doc: https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/
Modifications
Added a topology spread constraint configuration to deployed the pods in sts spread to different az, so that under an AZ outage, the impact can be only limited to small number of brokers.
Verifying this change