[tempo] Add topologySpreadConstraints #3460
Open
+10
−2
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: rim99 <[email protected]>
|
|
rim99
requested review from
Sheikh-Abubaker,
dgzlopes,
swartz-k,
BitProcessor,
faustodavid and
a team
as code owners
Signed-off-by: rim99 <[email protected]>
rim99
force-pushed
the
tempo_add_topology_spread_constraints
branch
from
3f02ea4 to
89c0c27
Compare
|
Hey @Sheikh-Abubaker, I've updated this PR as the linter suggested. Would you like to review this? |
|
isn't this a single binary helm chart? do topology constraints impact a single pod statefulset? |
|
@joe-elliott I think this can be tuned to be a statefulset with mutiple pods. |
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.
Add topologySpreadConstraints, so pods can spread in multiple AZs or regions evenly