If you work with multiple Kubernetes clusters, you likely know the pain. You switch contexts with `kubectx`, run a command in another terminal, and realize you just targeted the wrong cluster because `KUBECONFIG` is global. Or you find yourself manually setting environment variables to ensure each terminal targets the correct cluster. This is where [**kubert**](https://github.com/idebeijer/kubert) comes in. Inspired by kubie (more on that later), `kubert` is an alternative to `kubectx` and `kubens` combined, but with a key difference: **isolation**. ## How It Works Instead of modifying your global kubeconfig file, `kubert` manages a separate, temporary kubeconfig for each shell session. When you run `kubert ctx <context>`, it spawns a new subshell with a dedicated `KUBECONFIG` pointing to a temporary file. This means you can have multiple terminals open, each pointing to a different cluster and namespace, without them ever interfering with each other. Values are set for that sess...