Add topology spread constraint to kvdb for specific distribution of kv store #1663
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
…rce-distributed across a specific zonal designation without the label selectors Signed-off-by: jmcshane <jmcshane@purestorage.com>
|
The scheduling control is handled earlier in the operator, so this does not do anything. Closing |
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.
While kvdb labeling can enable us to force the kvdb pods onto specific nodes,
this creates an issue when those nodes fail. To resolve this, topology spread constraints allow
Kubernetes users to spread these pods across specific failure domains, whether they are
zones, racks, or other user defined topologies.
What this PR does / why we need it:
Add topologySpreadConstraint to kvdb configuration