ahmetb/kubectx — 20.1k★ on GitHub (Go). Faster way to switch between clusters and namespaces in kubectl
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This repository provides both kubectx and kubens tools.
Install →
What are kubectx and kubens?
kubectx is a tool to switch between contexts (clusters) on kubectl
faster, and launch readonly shells for each context. kubens is a tool to switch between Kubernetes namespaces (and
configure them for kubectl) easily.
Here's a kubectx demo:
...and here's a kubens demo:
Usage
kubectx
Switch to another cluster that's in kubeconfig:
$ kubectx minikube
Switched to context "minikube".
Switch back to previous cluster:
$ kubectx -
Switched to context "oregon".
Start an isolated shell that only has a single context:
$ kubectx -s minikube
Start a read-only shell where write operations are blocked:
$ kubectx -r minikube
Rename context:
$ kubectx dublin=gke_ahmetb_europe-west1-b_dublin
Context "gke_ahmetb_europe-west1-b_dublin" renamed to "dublin".
kubens
Change the active namespace on kubectl:
$ kubens kube-system
Context "test" set.
Active namespace is "kube-system".
Go back to the previous namespace:
$ kubens -
Context "test" set.
Active namespace is "default".
Change the active namespace even if it doesn't exist:
$ kubens namespace-404 -f
Context "test" set.
Active namespace is "namespace-404".
If you have fzf installed, you can also
interactively select a context or cluster, or fuzzy-search by typing a few
characters. To learn more, read interactive mode →
Both kubectx and kubens support Tab completion on bash/zsh/fish
shells to help with long context names. You don't have to remember full context
names anymore.
Installation
Package manager
Command
Homebrew (macOS & Linux)
brew install kubectx
MacPorts (macOS)
sudo port install kubectx
apt (Debian/Ubuntu)
sudo apt install kubectx
pacman (Arch Linux)
sudo pacman -S kubectx
Chocolatey (Windows)
choco install kubens kubectx
Scoop (Windows)
scoop bucket add main && scoop install main/kubens main/kubectx
Alternatively, download binaries from the Releases page → and add them to somewhere in your PATH.
Shell completion scripts
zsh (with antibody)
Add this line to your Plugins File (e.g.
~/.zsh_plugins.txt):
ahmetb/kubectx path:completion kind:fpath
Depending on your setup, you might or might not need to call compinit or
autoload -U compinit && compinit in your ~/.zshrc after you load the Plugins
file. If you use oh-my-zsh, load the
completions before you load oh-my-zsh because oh-my-zsh will call
compinit.
zsh (plain)
The completion scripts have to be in a path that belongs to $fpath. Either
link or copy them to an existing folder.
If completion doesn't work, add autoload -U compinit && compinit to your
.zshrc (similar to
zsh-completions).
If you are not using oh-my-zsh, you
could link to /usr/share/zsh/functions/Completion (might require sudo),
depending on the $fpath of your zsh installation.
[!NOTE]
Tip: Show context/namespace in your shell prompt with oh-my-posh or
simply with kube-ps1.
Interactive mode
If you want kubectx and kubens commands to present you an interactive menu
with fuzzy searching, you just need to install
fzf in your $PATH.
Caveats:
If you have fzf installed, but want to opt out of using this feature, set the
environment variable KUBECTX_IGNORE_FZF=1.
If you want to keep fzf interactive mode but need the default behavior of the
command, you can do it by piping the output to another command (e.g. kubectx | cat ).
Customizing colors
If you like to customize the colors indicating the current namespace or context,
set the environment variables KUBECTX_CURRENT_FGCOLOR and
KUBECTX_CURRENT_BGCOLOR (refer color codes
here):
export KUBECTX_CURRENT_FGCOLOR=$(tput setaf 6) # blue text
export KUBECTX_CURRENT_BGCOLOR=$(tput setab 7) # white background
Colors in the output can be disabled by setting the
NO_COLOR environment variable.
If you liked kubectx, you may like my
kubectl-aliases project, too. I
recommend pairing kubectx and kubens with fzf and
kube-ps1.
Yes — ahmetb/kubectx ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/ahmetb/kubectx.
What else is in the Developer Tools space?
ahmetb/kubectx is tracked by TopGit under the Developer Tools category, alongside 4 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is ahmetb/kubectx?
ahmetb/kubectx (ahmetb/kubectx) is a Go project on GitHub. From the project's own README: Faster way to switch between clusters and namespaces in kubectl
What license does ahmetb/kubectx use?
ahmetb/kubectx is released under the Apache-2.0 license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where can I see ahmetb/kubectx in action?
The project maintains a homepage at https://kubectx.dev. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about ahmetb/kubectx?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ahmetb/kubectx is the definitive source.
Why is ahmetb/kubectx categorized under Developer Tools?
TopGit places ahmetb/kubectx in the Developer Tools category based on its GitHub topics and description (tagged: "kubectl", "kubectl-plugins", "kubernetes"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Is kubectx worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of kubectx.