-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
LimitRange ignores objects previously marked for deletion #56971
LimitRange ignores objects previously marked for deletion #56971
Conversation
/lgtm |
bot /approve this as i gave an issue. |
Why is limitrange paying attention to updates? |
If memory serves, you can update the amount of request resources on pods, rigth? |
no... only image, activeDeadlineSeconds, and tolerations |
/retest |
i think it was historical w/ pvc capacity, but memory escapes me. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, dixudx Associated issue: #57201 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 |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 56971, 57570, 57830, 57742). If you want to cherry-pick this change to another branch, please follow the instructions here. |
Automatic merge from submit-queue. UPSTREAM: 56971: LimitRange ignores objects previously marked for deletion kubernetes/kubernetes#56971 xref https://bugzilla.redhat.com/show_bug.cgi?id=1509309 @derekwaynecarr
What this PR does / why we need it:
A
LimitRange
added to a namespace after it has pods can prevent terminating pods from being deleted if they do not conform to the min/max criteria.xref https://bugzilla.redhat.com/show_bug.cgi?id=1509309
Fixes #57201