-
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
Check if context is invalid during update-context #15032
Conversation
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube ingress: 24.1s 25.6s 24.6s 29.1s 29.1s Times for minikube start: 55.6s 54.2s 55.7s 55.9s 54.5s docker driver with docker runtime
Times for minikube (PR 15032) start: 28.2s 28.0s 27.5s 27.5s 28.6s Times for minikube ingress: 26.5s 23.0s 23.5s 21.5s 23.5s docker driver with containerd runtime
Times for minikube start: 22.9s 22.3s 36.8s 22.9s 22.9s Times for minikube ingress: 27.5s 27.5s 27.0s 27.5s 27.5s |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh, spowelljr 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 |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
Closes #15039
Previously only the cluster was checked when
minikube update-context
was called. Now the context is checked as well, and if either is invalid it recreates the entries.