-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Allow override of cluster level (default, whitelist) tolerations by namespace level empty (default, whitelist) tolerations. #17116
Conversation
/unassign |
/test unit |
… tolerations by namespace level empty (default, whitelist) tolerations.
d8afb6f
to
83d3756
Compare
/kind bug |
/lgtm |
@derekwaynecarr could you approve it? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aveshagarwal, derekwaynecarr, sjenning The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue. |
Currently In PodTolerationRestriction admission plugin, if namespace level default and whitelist of tolerations are nil or empty, they do not override cluster level default and whitelist tolerations.
This PR fixes the plugin to not override cluster level tolerations only when namespace level toleration are nil. IOW, if namespace level toleration are empty, they override cluster level tolerations. To be more clear, if following annotations are set to empty, they override cluster level tolerations.
This behavior is inline with PodNodeSelector admission plugin too.
@sjenning
I think its important to get it fixed for 3.7 so creating this backport PR even though the upstream PR is not merged yet.