Feature request: ability to set the current context to "none".

[stremblay]

Hello!

First, I love the fact that you ported kubectx to PowerShell. This is really cool!

I would love to have a feature to set the context to "none" or empty. Is that possible? This would help to potentially avoid running commands by accident using the history and messing up a customer's production environment cluster for example.

Regards,

Stéphane

[thomasliddledba]

Hi @stremblay
I think this is a great feature idea. I'll work on something this weekend.

Thanks

[thomasliddledba]

I'll be modifying this code

kubectxwin/kubectxwin.ps1

Lines 50 to 52 in d0f6e22

	function switch_context($context) {
	kubectl config use-context $context
	}

to the following

function switch_context($context) {
    if ($context -eq 'n/a') {
        kubectl config set-context no-context
        kubectl config use-context no-context
    }
    else {
        kubectl config use-context $context
    }
}

I'm using the n/a because namespaces can't use special characters referenced in RFC 1123 for creating namespaces.

kubectl create ns n/a
The Namespace "n/a" is invalid: metadata.name: Invalid value: "n/a": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')

[thomasliddledba]

Hi @stremblay
I made the changes requested. Let me know if you have any questions or issues.

Thanks.

[stremblay]

Amazing! Thank you! I will update immediately and let you know. :)

[stremblay]

In case you want to make your tool as similar to the Linux kubectx, I think they use a flag such as -u --unset which I just found out was added last year.
kubectx -u, --unset : unset the current context

This could be an alternative as well.

[thomasliddledba]

I like the unset option also. I'll add that. Give me a few days.