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

Why is this better than kubectl config use-context? #2

Open
andremarianiello opened this issue Aug 23, 2017 · 3 comments
Open

Why is this better than kubectl config use-context? #2

andremarianiello opened this issue Aug 23, 2017 · 3 comments

Comments

@andremarianiello
Copy link

andremarianiello commented Aug 23, 2017

kubectl already has a way to set your current context (kubectl config use-context). Why would I use this instead?

@mcronce
Copy link

mcronce commented Aug 23, 2017

+1

@philipn
Copy link
Owner

philipn commented Aug 23, 2017

I don't think it was possible when I first wrote this utility. See e.g. kubernetes/kubernetes#10735. It looks like kubectl config use-context does the trick now, though. The only drawback is that it doesn't provide a cue in the shell.

@philipn
Copy link
Owner

philipn commented Aug 26, 2017

@andremarianiello It may also be worthwhile to ask this of https://github.com/ahmetb/kubectx, as the maintainer is also on the Kubernetes team.

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

No branches or pull requests

3 participants