what is kush fr?

kush is a command line tool for people who work with Kubernetes, the system many companies use to run containerized applications across clusters of servers. Normally, switching which cluster or environment kubectl points to means editing a single shared configuration file, and that change affects every terminal window, script, and background tool reading that same file. It is easy to end up accidentally running a command against production because another terminal changed the active context a few minutes earlier. kush solves this by never touching that shared file. Running kush with a context name, such as prod, opens a normal subshell that is pinned to that one context through its own private, temporary configuration file. Any kubectl, helm, or similar tool run inside that shell only sees the pinned context. When you exit the shell, the temporary configuration is deleted automatically, so nothing persists and your main setup is untouched. You can have a prod shell open in one terminal and a dev shell in another at the same time, with no risk of one leaking into the other. Because kush copies the authentication details from your existing configuration exactly as they are, it keeps working with whatever login method you already use, including cloud provider logins and OpenShift. It ships as a single Go binary with no other dependencies, and can be installed through Homebrew, the kubectl plugin manager Krew, Nix, or by building from source. It is unix-only for now, so it does not support Windows. Beyond the basic enter and exit workflow, kush includes commands for re-pinning just the namespace inside an existing shell, running a single command against a context without opening an interactive shell, checking configuration files for common problems, and splitting a shared configuration into separate files per context. Configuration is optional, with sensible defaults, and can include hooks that run commands automatically when entering or leaving a context. This is aimed at developers and operations engineers who regularly switch between multiple Kubernetes clusters and want to avoid running commands against the wrong one by mistake.