-
Notifications
You must be signed in to change notification settings - Fork 1.5k
use a dedicated config to disable default pod affinity #2743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use a dedicated config to disable default pod affinity #2743
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2743 +/- ##
=======================================
Coverage 53.99% 53.99%
=======================================
Files 144 144
Lines 8214 8214
=======================================
Hits 4435 4435
Misses 3461 3461
Partials 318 318 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kishorj, M00nF1sh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
revert changes from PR kubernetes-sigs#2576
1de7990
to
b66b48a
Compare
New changes are detected. LGTM label has been removed. |
/retest |
/lgtm |
) revert changes from PR kubernetes-sigs#2576
Issue
Alternate fix for issue #2570
Description
This PR revert changes from #2576 and adds a separate helm value
configureDefaultAffinity
which controls whether to use the default affinity configuration for the controller pods. This value is true by default, so there is no changes in the behavior from prior version. In case of custom affinity configuration, this value gets ignored.Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯