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

Feature: Set as current Cluster #50

Closed
SeriousM opened this issue Mar 19, 2020 · 3 comments · Fixed by #72
Closed

Feature: Set as current Cluster #50

SeriousM opened this issue Mar 19, 2020 · 3 comments · Fixed by #72
Labels
enhancement New feature or request

Comments

@SeriousM
Copy link

Hi!

kubectl has the ability to set a cluster as the "current" one so that every command is executed on the current selected cluster.
Could you add an option to the windows/linux version which triggers the kubectl command to set the current cluster to the one selected in kubenav?

Best regards, Bernhard

@ricoberger
Copy link
Member

Hi @SeriousM and sorry for the late reply. I like the idea of switching the current context via kubenav. I'm not sure if everyone wants this behavior, therefor this could be an optional parameter in the configuration.

Unfortunately I cannot promise when this feature will be implemented, but I will take a look at it.

@ricoberger ricoberger added the enhancement New feature or request label Apr 13, 2020
@SeriousM
Copy link
Author

Thank you Sir!

@ricoberger
Copy link
Member

Hi, it's now possible to save changes to the context and namespace back to your Kubeconfig file. You can use the build from here to test this feature: https://github.com/kubenav/kubenav/actions/runs/113134412

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants