Skip to content
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

Closed
kschaab opened this issue Aug 14, 2020 · 3 comments
Closed

Support --keep-context parameter on minikube stop #9001

kschaab opened this issue Aug 14, 2020 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@kschaab
Copy link
Contributor

kschaab commented Aug 14, 2020

Please add the --keep-context parameter to minikube stop so that we can indicate to minikube to not switch contexts on stop.

@medyagh medyagh added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 14, 2020
@medyagh
Copy link
Member

medyagh commented Aug 14, 2020

current behaviour:

medya@~/workspace/campwiz (master) $ kubectl config get-contexts
CURRENT   NAME       CLUSTER    AUTHINFO   NAMESPACE
          minikube   minikube   minikube   
*         p2         p2         p2         
          p3         p3         p3         

medya@~/workspace/campwiz (master) $ minikube stop -p p2
✋  Stopping node "p2"  ...
🛑  Powering off "p2" via SSH ...
🛑  1 nodes stopped.


medya@~/workspace/campwiz (master) $ kubectl config get-contexts
CURRENT   NAME       CLUSTER    AUTHINFO   NAMESPACE
          minikube   minikube   minikube   
          p2         p2         p2         
          p3         p3         p3   

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 kubectl config get-contexts

Medya Ghazizadeh, Now
so I am not yet convinced if this is a feature that minikube should add, but I open to be convinced

@kschaab
Copy link
Contributor Author

kschaab commented Aug 15, 2020

I agree, I'm not sure how useful this is.

@sharifelgamal
Copy link
Collaborator

This is fixed by #9044

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants