-
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
Support --keep-context parameter on minikube stop #9001
Comments
current behaviour:
in kubectl config get-contexts but it does NOT have a * on it because it is not Active so you want us to Active the context, even though there is no cluster ? I suspect that would add all sort of weird issues, such as you would get Api Errors, when you do, kubectl get pods why would you want a Not Actibe cluster to be shown active? if you want list of all context (including not active ones, you can get it form Medya Ghazizadeh, Now |
I agree, I'm not sure how useful this is. |
This is fixed by #9044 |
Please add the
--keep-context
parameter tominikube stop
so that we can indicate to minikube to not switch contexts on stop.The text was updated successfully, but these errors were encountered: