kubie

In addition to the other recommendations, I always suggest Kubie (https://github.com/sbstp/kubie). The nice thing about Kubie is that it spawns a new shell when you select a kubeconfig, meaning selecting a Kubernetes context in one terminal window doesn't clobber what you're doing in another.

you seen kubie? `kubie ctx` is great for avoiding the first issue https://github.com/sbstp/kubie

Have been burnt by this, I have to deal with close to 8 clusters and it is very easy to make a mistake. Would highly recommend kubie, it allows you to switch and shows you the name of the cluster in the prompt. It's probably a more visual way of solving the same problem. https://github.com/sbstp/kubie

Yeah, fair points. Regarding (3) there are tools for that like kubie. I've still shot myself in the foot before. https://github.com/sbstp/kubie

I have an edge-case for zsh completion that I'd love to know if there's a way to implement. I've declared a function `k` which tests if I'm currently on a `kubie` [0] shell. If it isn't, it runs `kubie ctx`; if it is, it runs `kubectl $@`. I never write kubectl directly but rather run this `k` function. This way I'm always in the context I want and don't get surprises since I'm forgetful. I'd like for this function to complete like it was kubectl itself. So far I've tried: compdef k=kubectl compdef _kubectl k compdef '_bash_complete -o default -F __start_kubectl' k The last one is from the below, although I don't really understand what it's doing: $ grep kubectl ~/.zcompdump 'kubectl' '_bash_complete -o default -F __start_kubectl' autoload -Uz _bat _brew _git _j _kubectl \ [0] https://github.com/sbstp/kubie

Kubie makes it easier (and safer) to manage multiple contexts because it makes each shell independent: https://github.com/sbstp/kubie