kubectx VS kubesess

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.

You can find it here: kubesess

I wrote a similar tool in rust! Super happy with it kubesess!

If you don’t have a local cluster, you could always bypass Argo and deploy straight to dev cluster, just turn off auto deploy first. I use my own tool to navigate clusters (kubesess

I’ve created a tool, kubesess, that does just that! I use it myself daily, it’s super fast, some would say BLAZINGLY FAST program written I rust.

You should take a look into kubesess. I wrote it because I wanted a fast and lightweight way of doing context per session

I am also the author of another cli tool called kubesess that helps with session-based contexts.

You can find it here: Ramilito/kubesess: Kubectl plugin managing sessions (github.com)

kubesess (repo) is a tool for handling contexts in kubernetes and shines when you have many contexts!