[BCDR] feat: Update podAntiAffinity #84
Merged
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.
List of Changes
Update with
preferredDuringSchedulingIgnoredDuringExecution
:The scheduler tries to find a node that meets the rule. If a matching node is not available, the scheduler still schedules the Pod.
100
, this specifies the weight of this anti-affinity rule.topology.kubernetes.io/zone
, the node must have a label with the keytopology.kubernetes.io/zone
Motivation and Context
This pod anti-affinity rule ensures that pods with the
app.kubernetes.io/instance: pagopagpdpayments
label are spread across different availability zones in the gps namespace.How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: