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 integration test servers extra time to start #93398
Allow integration test servers extra time to start #93398
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
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
/retest
/retest Review the full test history for this PR. Silence the bot with an |
including in the milestone to improve CI signal |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
2 similar comments
/retest |
/retest |
/remove-triage needs-information |
What type of PR is this?
/kind flake
What this PR does / why we need it:
In CI environments without reserved resources for the test pod, the CPU dedicated to an individual integration test can be much lower than expected. The test apiserver has much more to do during startup before /healthz will return healthy (all post-startup hooks have to complete), and occasionally this does not complete within 30 seconds.
See https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&text=%2Fhealthz&job=pull-kubernetes-integration
Avoid failing tests due to unrelated CPU starvation.
Does this PR introduce a user-facing change?:
/sig api-machinery
/cc @deads2k