-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 users to skip pod health checks with --wait=false #4744
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tstromberg 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 |
2022029
to
44c8dd5
Compare
@minikube-bot OK to test |
/retest this please |
If you change your mind (or your cluster is acting weird), can you run the health checks afterwards ? |
Not yet, but you bring a good point. We should extend |
@minikube-bot OK to test The one failure here appears to be #4418 - just looking for more test data:
|
@minikube-bot OK to test |
@minikube-bot OK to test |
PTAL - passes all tests, amazingly. |
This saves about 1 minute of run time, and will be useful for integrating with other applications which may do their own health checking. This flag behaves the same as the similarly named flag in
kind
, with one important difference: we leave the default astrue
for a more predictable start-up sequence, at the expense of startup latency. This was also the behavior in minikube up until v1.0.This PR also sets
--wait=false
to all tests where it's possible to begin testing without all of the services online, such as CoreDNS or etcd. As a result, this PR decreases integration testing time by ~9 minutes.