Update default operator podAntiAffinity #2475
Open
Conversation
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
Target the actual deployment labels.
ramondeklein
approved these changes
Jul 25, 2025
ramondeklein
requested review from
pjuarezd,
cniackz,
JoelRuizRojas and
dvaldivia
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.
Description
Target the actual existing deployment pod labels.
There is no
namelabel on the operator pods.Additionally the label value was changed 4 years ago in dd62a26 from
minio-operatortooperator.Related Issue
Type of Change
Screenshots (if applicable e.g before/after)
Checklist
Test Steps
Additional Notes / Context
Having the current
app.kubernetes.io/name: operatorlabel should probably be adjusted as well since this may collide with other pods.The original label before the above change was
app.kubernetes.io/name: minio-operator.