-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Cherry limit 05 #2105
Cherry limit 05 #2105
Conversation
The test relied on order of iterating through map.
Prepare for setting limits
- Name test cases, - Drop duplicated test case, - Simpler error handling of invalid expected resource amounts, - Format code more in line with other tests.
/assign @bskiba |
/hold Actually I think it will be cleaner if cherry pick all commits in a single PR |
Users should use ContainerResourcePolicy if they want to control VPA recommendation range.
Except when proportion is huge and recommendation is huge which would result in milli limit exceeding int64 maximum. Then cap the limit milli value to int63 max.
I think it's useful to revers condtions in the tests when dropping capping to limits to make sure are the relevant code is gone. I don't think it's an useful test to keep around.
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bskiba 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 |
Cherry pick: