kubectx VS kubeswitch

kubectx: brew install kubectx

default is where any actions which require a namespace will go into if one is not explicitly defined in a default setup (tools such as kubens can alter this behavior). In the context of Jenkins, namespaces are a useful way to allow isolation of individual Jenkins instances that want to utilize the same Kubernetes cluster. Creation of a namespace is a simple option to kubectl:

Here you go: https://github.com/ahmetb/kubectx and https://kubecm.cloud/

check out kubectx/kubens https://github.com/ahmetb/kubectx very handy tool to permanently switch context/namespace

kubectx + kubens v0.9.4

For a peek at what's currently possible, visit the documentation site, in particular the Usage section. For this initial release, it has feature parity with kubectx and kubens and that's about it, but there's lots of room for growth.

I also encourage you to install kubectx + kubens to navigate Kubernetes easily.

switched from kubectx to kubeswitch

You can just install kubeswitch , it's easy to use and it's better than kubectx and kubie

kubeswitch

https://github.com/danielfoehrKn/kubeswitch does this and more. It’s pretty good. I switched to it from kubectx/kubens

I’ve been very happily using kubeswitch for this as well.

If you are looking for an alternative to kubectx and kubens, that has terminal window isolation, a context history and works well for multi-cloud, I invite you to check out switch. No need for fzf binary as fuzzy search is integrated.

Kubeswitch got some exciting new features and contributions. I am sharing this because I think this tool can be a great productivity booster for many of you. Looking for contributions to eventually support all common Cloud Providers (thanks Meroje for contributing EKS support!).

You can check out https://github.com/danielfoehrKn/kubeswitch. Also comes with isolated terminal sessions + other advanced features such as history support and integration with GKE, AKS, Gardener, Vault & soon more.