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.

Sign up for GitHub

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

Jump to bottom

Feature Request - unset current-context after minikube stop #4154

Closed
davidmnoriega opened this issue Apr 25, 2019 · 1 comment
Closed

Feature Request - unset current-context after minikube stop #4154

davidmnoriega opened this issue Apr 25, 2019 · 1 comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@davidmnoriega
Copy link

Working with multiple kube clusters, it is useful to have the context in my shell prompt, and I can use the kubectl command to switch between them. If minikube start automatically sets the current context to itself, why not then unset it on minikube stop?
@tstromberg tstromberg added kind/feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Apr 25, 2019
@tstromberg
Copy link
Contributor

Great idea! I love this idea and would be happy to review any PR which implements it. Thank you for the suggestion.

@tstromberg tstromberg added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Apr 25, 2019
@hpandeycodeit hpandeycodeit mentioned this issue Apr 30, 2019
Merged
@jdanlewis jdanlewis mentioned this issue Jun 12, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tstromberg @davidmnoriega