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 why I built **kubert**. Check it out on GitHub: [https://github.com/idebeijer/kubert](https://github.com/idebeijer/kubert). 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. It uses the context name as a unique identifier (so duplicates are not allowed). When you select a context, `kubert` looks up the corresponding cluster and user from your source kubeconfig, even if that file contains dozens of other clusters...