-
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
Don't enable kubelet at boot, for consistency with other components #4110
Don't enable kubelet at boot, for consistency with other components #4110
Conversation
Hi @marcosdiez. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: marcosdiez If they are not already assigned, you can assign the PR to them by writing 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 |
Can one of the admins verify this patch? |
/ok-to-test Alternatively - should we ever have this enabled on boot? I'd rather remove the special case on the none driver if possible. |
On second thought - yes, I think this PR would be better if it the logic was applied consistently so that we didn't enable kubelet across reboots for any drivers. VM reboots are for the time-being somewhat undefined - but my preference here is that |
@tstromberg good idea! Not making the kubernetes cluster start upon reboot is a better alternative for minikube. Now my PR is a one liner! |
Thanks! |
I am not sure if this should be an option or not. Again, what's the use case for
--vm-driver=none
?Every other app I run in my laptop does not silently reloads upon a reboot.
I expect Minikube to behave the same.
Thinking about it, it does not do that if we use any other driver, hence this PR makes things consistent!
That's a behavior change, so if you guys want I can add a command line parameter.
--dont-start-on-boot
for example. (suggestions are welcome)