Allow to unset the current-context (-u?)

[jorgemoralespou]

It would be nice if we could select current-context to empty, so unset the current-context, as for safety reasons, that would be similar (in effects) to logging off. This way, you can prevent commands being executed agains a cluster if any of the automation you're running does accidentally try to do something.

My workflow is similar to:

• going to work on something (login), so do kubectx my-context
• do my work
• finished working on a cluster (logout), so do kubectx -off (OR SIMILAR)

Using kubectx -d <CTX> does delete the context, but not unsets the current-context, so still has a value to a non existing context. What I'm requesting is the opposite, retain the context, but unset the value from current-context.

[ahmetb]

Does kubectx “” (empty string as arg) work?

[jorgemoralespou]

kubectx ""
error: empty context names are not allowed

[ahmetb]

@jorgemoralespou hmm looks like a this is a kubectl limitation. We primarily use kubectl to interact with kubeconfig, and never edit it directly (for a lot of reasons).

kubectl config set current-context ""
error: you cannot use set to unset a property

kubectl config use-context ""
error: empty context names are not allowed

It seems like kubectl can't do this. :(

On the other hand, given ~100k users we have and we're receiving this request for the first time, I'm inclined to think this is rather an exotic request. You can achieve what you want by setting something like KUBECONFIG=/dev/null in your shell.

[rsalmond]

@ahmetb the command you're looking for is kubectl config unset current-context

[rux616]

I actually just came here looking for the same thing. It could also be useful to have a flag to specify the fact that you want to unset the current context, maybe something like -u:

kubectx -u

[ahmetb]

Thanks, yeah I am currently still -1 for adding a feature for this to kubectx, need more evidence that this is a real user need (especially since kubectl can already do it).

[rux616]

Thanks, yeah I am currently still -1 for adding a feature for this to kubectx, need more evidence that this is a real user need (especially since kubectl can already do it).

That's fair. I have just gotten used to manipulating my context through kubectx since it makes it much easier.

[rsalmond]

kubectl can already do it

kubectl can already do config use-context too, I'm here for the shell sugar!

[jorgemoralespou]

Totally agree. I'm really surprised this has not come up before, as leaving the context set is almost as being always logged into the cluster. Any thing that we do might be executed on the current context/cluster we have set.
I understand that many users don't work with multiple clusters, and that when you have PS1 indicating you the context you have selected is really obvious you want it set/unset when working/not working on stuff on the cluster.

[ahmetb]

I think simply, most users don't want to unset kubectl, because it leaves kubectl malfunctional. Most people dealing with multiple kubeconfig files can simply unset KUBECONFIG and get the same behavior. This is probably why it didn't come up before.

[rsalmond]

Yeah that is spot on. Leaving kubectl (and other client-go tools which understand kubeconfig) malfunctioning is precisely my use case. For those of us not using multiple config files unsetting the current-context is the next best thing.