[prometheus-yet-another-cloudwatch-exporter] Add topologySpreadConstraints support#6943
Open
lucasbn wants to merge 1 commit into
Open
Conversation
…aints support Signed-off-by: Lucas Graeff Buhl-Nielsen <lucas.buhl-nielsen@quantco.com>
lucasbn
requested review from
andriikushch,
cristiangreco,
thomaspeitz and
tristanburgess
as code owners
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this PR does / why we need it
Adds
topologySpreadConstraintsto the deployment manifest for theprometheus-yet-another-cloudwatch-exporterso that it can be run with multiple replicas spread across different nodes/zones. Without topology spread constraints, running multiple replicas for HA provides limited benefit if all pods land on the same node/zone.Checklist
[prometheus-couchdb-exporter])