-
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
Implement scheduled stop on windows #9689
Conversation
/ok-to-test |
kvm2 Driver |
kvm2 Driver Times for Minikube (PR 9689): 53.3s 54.8s 58.7s Averages Time Per Log
docker Driver Times for Minikube (PR 9689): 30.1s 28.0s 27.9s Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 9689): 55.6s 53.0s 54.4s Averages Time Per Log
docker Driver Times for Minikube (PR 9689): 28.4s 27.4s 26.7s Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 9689): 52.4s 55.2s 58.3s Averages Time Per Log
docker Driver Times for Minikube (PR 9689): 27.2s 27.3s 27.5s Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 9689): 23.3s 56.5s 54.2s Averages Time Per Log
docker Driver Times for Minikube (PR 9689): 26.6s 28.2s 27.3s Averages Time Per Log
|
TODO: build ISO/kicbase as a snapshot version and test with those |
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.
approve with required testing upgrading k8s version
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh, priyawadhwa 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 |
@medyagh tested with k8s version upgrade, this still works as expected |
kvm2 Driver Times for Minikube (PR 9689): 58.8s 57.3s 55.1s Averages Time Per Log
docker Driver Times for Minikube (PR 9689): 29.4s 27.9s 26.7s Averages Time Per Log
|
Implements scheduled stop on windows.
This PR creates a minikube-scheduled-stop systemd service which is responsible for shutting down minikube from within. When a user runs:
then minikube will:
The systemd service reads the value of SLEEP and sleeps that amount of time. It then powers off minikube from within.
Cancelling old scheduled stops is as simple as running
sudo systemctl stop minikube-scheduled-stop
within minikube.Tested the integration test on our windows instance with hyperv and docker and it passes.
Part of #9271