-
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
Set --wait=false to default but still wait for apiserver #5757
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Codecov Report
@@ Coverage Diff @@
## master #5757 +/- ##
==========================================
+ Coverage 37.83% 37.86% +0.02%
==========================================
Files 106 106
Lines 7773 7796 +23
==========================================
+ Hits 2941 2952 +11
- Misses 4452 4464 +12
Partials 380 380
|
This PR changes --wait=false to be the default, but to still check for the apiserver in this case. If wait=true, we still wait for all pods to be up and running. This change should speed up `minikube start`, since we won't have to wait for other pods which can take a longer time to start up. Ref kubernetes#5681
e5aecf2
to
f92b308
Compare
Running mkcmp on this branch vs master on my Mac with hyperkit show significant speedup: Logs $ ./out/mkcmp ./out/master.minikube ./out/wait_false.minikube
2019/10/28 10:34:13 Executing run 0...
2019/10/28 10:34:13 Running: [./out/master.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"
2019/10/28 10:36:50 Running: [./out/wait_false.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver
🏄 Done! kubectl is now configured to use "minikube"
2019/10/28 10:38:04 Executing run 1...
2019/10/28 10:38:04 Running: [./out/master.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"
2019/10/28 10:40:42 Running: [./out/wait_false.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver
🏄 Done! kubectl is now configured to use "minikube"
2019/10/28 10:41:59 Executing run 2...
2019/10/28 10:41:59 Running: [./out/master.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"
2019/10/28 10:44:32 Running: [./out/wait_false.minikube start]...
😄 minikube v1.5.0 on Darwin 10.14.6
🔥 Creating hyperkit VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.16.2 on Docker 18.09.9 ...
🚜 Pulling images ...
🚀 Launching Kubernetes ...
⌛ Waiting for: apiserver
🏄 Done! kubectl is now configured to use "minikube"
Old binary: [151.380704891 152.648160101 147.704785009]
New binary: [69.619480977 71.68093154 66.499298735]
Average Old: 150.577883
Average New: 69.266570 Old binary: [151.380704891 152.648160101 147.704785009] |
wow what a big difference, I am curious which one of the integration tests would need to pass --wait=false |
/ok-to-test |
Do you mind confirming that
Please add an integration test that asserts here right after startup here:
I suggest using |
Current integration tests appear to be unrelated flakes. Great work! =) |
@tstromberg I check if we can get the apiserver pod here without error, do you think that's enough? (It shouldn't return |
to make sure apiserver is up and running and that the pod can be accessed via kubectl.
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.
This PR is awesome, and completely overdue.
Your PR is doing the right thing. The integration test is so that future contributors do not unknowingly change this behavior. |
when waiting for the cluster to start up.
59978e1
to
bd5840a
Compare
@tstromberg sounds good! I removed updating the docs from this PR, it was getting large/complicated and it'll be easier to review it in a separate PR. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: priyawadhwa, 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 |
This PR changes --wait=false to be the default, but to still check for the apiserver in this case. If wait=true, we still wait for all pods to be up and running. This change should speed up
minikube start
, since we won't have to wait for other pods which can take a longer time to start up.Ref #5681
Output now looks like:
TODO: