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 pick stabilizing HPA e2e tests to 1.11 #70736
Cherry pick stabilizing HPA e2e tests to 1.11 #70736
Conversation
ea8570c
to
2bffa86
Compare
/ok-to-test |
2bffa86
to
ad88771
Compare
Changes: - Relax stabilization requirement. Size may increase by 1 during stabilization. This is because HPA now stabilizes on max recommendation in the stabilization window. So if it sees a higher sample it should scale up. Resource consumer is imperfect and generates higher samples sometimes. - Lower CPU load generated during stabilization period. This reduces risk of generating samples much higher than expected. - Log status of HPA for easier debugging if the test fails. - Increase expected number of millicores used to handle request to generate usage (see 7d2f3a0). - Change int32 fields that were always cast to int before use to int. - Update boilerplate.
ad88771
to
a0cc3b6
Compare
Issue #70655 |
/assign @MaciekPytel |
/lgtm |
/assign @janetkuo |
/lgtm |
/lgtm |
@foxish 1.11 patch manager for CP request. This CP into 1.11 is critical to get a clean CI Signal for 1.13 |
Done, approved. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: jbartosik, MaciekPytel 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 |
What type of PR is this?
What this PR does / why we need it: HPA e2e tests are failing in 1.11. I fixed them on HEAD but they're failing in 1.11.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Issue #69444
Special notes for your reviewer:
Does this PR introduce a user-facing change?: