kconf VS kubie

To anyone visiting here, I got a lot of feedback for new tools (which I haven't tried yet), both on Youtube and here, so I compiled it into a list: A comment on Lens: Initially I wanted to include Lens in the video but decided it's a bit different in that it's not a CLI / TUI. Many users shared bad experience with Lens, mainly around performance and a large amount of requests it shoots at the cluster API to a point where some companies banned it. These are the tools (I may add a video review on if anyone thinks it's worth it): * https://github.com/kubermatic/fubectl - for an improved kubectl experience * https://github.com/particledecay/kconf - for those with complex kubeconfig changes requirements * https://github.com/MuhammedKalkan/OpenLens - an open version of Lens (note the above before using) * https://github.com/hidetatz/kubecolor - colored kubectl output :) * https://github.com/astefanutti/kubebox - the K9s little brother? * https://github.com/bergerx/kubectl-status - human friendly resource status output

See my other comment re: kconf. It's as simple as kconf add /my/file.conf. You could also pipe in from stdin (like if you're reading from Vault): vault kv get -field=kubeconfig /path/to/conf | kconf add.

Kubie is what you need.

Kubie

I can highly recommend kubie: https://github.com/sbstp/kubie I use it exactly because it launches a sub-shell with the choosen context and no other.

I have been using a similar tool [kubie](https://github.com/sbstp/kubie), would love to check how you are doing it

I've been using https://github.com/sbstp/kubie and has served me well

I currently use kubie (https://github.com/sbstp/kubie). Any idea how both compare?

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

kubie. I don't use it for context switching (still prefer kubectx!) but kubie exec is a really powerful tool for executing the same command across multiple contexts at once.

Kubie (not necessary)