fix(multicluster): affinities for controllers #14028
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.
Fixes #14008
In the linkerd-multicluster chart (or via
linkerd mc install|upgrade), settingenablePodAntiAffinity: truefor specific multicluster controllers or globally was causing the following error:The problem was with the PodDisruptionBudget manifest not passing the proper context to the
annotations.created-bypartials.Also, the
nodeAffinitysetting wasn't being taken into account for such controllers.The output can be tested with
bin/linkerd mc install -f values.yaml, using this asvalues.yaml(put something that makes sense for nodeAffinity, if you want to apply this to the cluster):