-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix Existing Requests and Limits with LimitRange #5269
Fix Existing Requests and Limits with LimitRange #5269
Conversation
/hold till #5082 is merged |
The following is the coverage report on the affected files.
|
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.
Thanks Austin! Would you mind splitting the limitrange commit into a separate PR?
@@ -310,7 +310,7 @@ func TestTransformerOneContainer(t *testing.T) { | |||
Containers: []corev1.Container{{ | |||
Resources: corev1.ResourceRequirements{ | |||
Limits: corev1.ResourceList{ | |||
corev1.ResourceMemory: resource.MustParse("4Gi"), | |||
corev1.ResourceMemory: resource.MustParse("2Gi"), |
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.
Thanks Austin! Nice job catching this bug, it looks like the behavior here wasn't consistent with our documentation. @vdemeester could you double check me here?
89ae4d1
to
be0d72c
Compare
/release-note-none |
/kind feature |
The following is the coverage report on the affected files.
|
be0d72c
to
c9be8d9
Compare
The following is the coverage report on the affected files.
|
c9be8d9
to
59cef74
Compare
/unhold |
The following is the coverage report on the affected files.
|
Fixes #5278 |
59cef74
to
337590a
Compare
337590a
to
4c77588
Compare
The following is the coverage report on the affected files.
|
/retest |
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.
We also need to address the test cases "limitRange with min and limits on containers < min" and "limitRange with max and requests on containers > max". These test cases are outputting invalid pods (requests > limits).
4c77588
to
141aa00
Compare
/hold cancel |
The following is the coverage report on the affected files.
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abayer 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 |
141aa00
to
10ebfd5
Compare
thanks @abayer for the review! pushed an update to ensure |
The following is the coverage report on the affected files.
|
/retest |
/hold till collecting further feedback from community |
LimitRange logic were updated to ensure the requests and limits of containers will be under the min and max range of LimitRange.
10ebfd5
to
580012b
Compare
The following is the coverage report on the affected files.
|
@austinzhao-go: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
closed the PR for this moment after a check with @lbernick the expected fix will be updated in another PR. |
Changes
This PR is to update
limitrange
logic to ensure container's requests and limits under the min and max range which is configured by limitrange./kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes