This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
charts/timescaledb-single: improve topology handling #528
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
|
Blocked by #529 |
paulfantom
force-pushed
the
topology
branch
3 times, most recently
from
f94f776 to
6edb196
Compare
Adding topologySpreadConstraints and removing `affinityTemplate` to allow easier handling of topology spread. Defaulting to kubernetes defaults when it comes to handling topology Signed-off-by: Paweł Krupa (paulfantom) <[email protected]>
nhudson
approved these changes
Jan 10, 2023
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adding topologySpreadConstraints and removing
affinityTemplateto allow easier handling of topology spread.Defaulting to kubernetes defaults when it comes to handling topology
Signed-off-by: Paweł Krupa (paulfantom) [email protected]
What this PR does / why we need it
affinityTemplateto allow only one way of setting affinity (viaaffinityfield). This should simplify UX.topologySpreadConstraintsWhich issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged)Special notes for your reviewer
Checklist