{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/312", "result": {"data":{"issuesJson":{"id":"f9c55655-a223-5c0e-a575-899241f31678","title":"ahmetb/kubectx: 在 kubectl 中更快速地切换不同集群和命名空间的方法","number":312,"bodyHTML":"

\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Repos	ahmetb/kubectx
Views	$\"views\"$
Stars	$\"stars\"$
Forks	$\"forks\"$
License	$\"license\"$
UpdatedAt	$\"last-commit\"$
CreatedAt	$\"create-at\"$

\n\n

\n

\n

\n

`kubectx` + `kubens`: Power tools for kubectl

\n

$\"Latest$
\n $\"GitHub$
\n $\"Homebrew$
\n $\"Go$
\n $\"Proudly$

\n

This repository provides both kubectx and kubens tools.
\nInstall →

\n

What are `kubectx` and `kubens`?

\n

kubectx is a tool to switch between contexts (clusters) on kubectl
\nfaster.

\nkubens is a tool to switch between Kubernetes namespaces (and
\nconfigure them for kubectl) easily.

\n

Here's a kubectx demo:
\n $\"kubectx$

\n

...and here's a kubens demo:
\n $\"kubens$

\n

Examples

\n

# switch to another cluster that's in kubeconfig\n$ kubectx minikube\nSwitched to context \"minikube\".\n\n# switch back to previous cluster\n$ kubectx -\nSwitched to context \"oregon\".\n\n# rename context\n$ kubectx dublin=gke_ahmetb_europe-west1-b_dublin\nContext \"gke_ahmetb_europe-west1-b_dublin\" renamed to \"dublin\".\n\n# change the active namespace on kubectl\n$ kubens kube-system\nContext \"test\" set.\nActive namespace is \"kube-system\".\n\n# go back to the previous namespace\n$ kubens -\nContext \"test\" set.\nActive namespace is \"default\".\n\n# change the active namespace even if it doesn't exist\n$ kubens not-found-namespace --force\nContext \"test\" set.\nActive namespace is \"not-found-namespace\".\n---\n$ kubens not-found-namespace -f\nContext \"test\" set.\nActive namespace is \"not-found-namespace\".

\n

If you have fzf installed, you can also
\ninteractively select a context or cluster, or fuzzy-search by typing a few
\ncharacters. To learn more, read interactive mode →

\n

Both kubectx and kubens support Tab completion on bash/zsh/fish
\nshells to help with long context names. You don't have to remember full context
\nnames anymore.

\n

\n

Installation

\n

Stable versions of kubectx and kubens are small bash scripts that you
\ncan find in this repository.

\n

Starting with v0.9.0, kubectx and kubens are now rewritten in Go. They
\nshould work the same way (and we'll keep the bash-based implementations around)
\nbut the new features will be added to the new Go programs. Please help us test
\nthis new Go implementation by downloading the binaries from the Releases page
\n→

\n

Installation options:

\n

\n

If you like to add context/namespace information to your shell prompt ($PS1),
\nyou can try out kube-ps1.

\n

Kubectl Plugins (macOS and Linux)

\n

You can install and use the Krew kubectl
\nplugin manager to get kubectx and kubens.

\n

Note: This will not install the shell completion scripts. If you want them,
\n*choose another installation method
\nor install the scripts manually.

\n

kubectl krew install ctx\nkubectl krew install ns

\n

After installing, the tools will be available as kubectl ctx and kubectl ns.

\n

Homebrew (macOS and Linux)

\n

If you use Homebrew you can install like this:

\n

brew install kubectx

\n

This command will set up bash/zsh/fish completion scripts automatically. Make sure you configure your shell to load completions for installed Homebrew formulas.

\n

MacPorts (macOS)

\n

If you use MacPorts you can install like this:

\n

sudo port install kubectx

\n

apt (Debian)

\n

sudo apt install kubectx

\n

Newer versions might be available on repos like
\nDebian Buster (testing),
\nSid (unstable)
\n(if you are unfamiliar with the Debian release process and how to enable
\ntesting/unstable repos, check out the
\nDebian Wiki):

\n

pacman (Arch Linux)

\n

Available as official Arch Linux package. Install it via:

\n

sudo pacman -S kubectx

\n

Windows Installation (using Chocolatey)

\n

Available as packages on Chocolatey

\n

choco install kubens kubectx

\n

Windows Installation (using Scoop)

\n

Available as packages on Scoop

\n

scoop bucket add main\nscoop install main/kubens main/kubectx

\n

Windows Installation (using winget)

\n

Available as packages on winget

\n

winget install --id ahmetb.kubectx\nwinget install --id ahmetb.kubens

\n

Manual Installation (macOS and Linux)

\n

Since kubectx and kubens are written in Bash, you should be able to install
\nthem to any POSIX environment that has Bash installed.

\n

Download the kubectx, and kubens scripts.
Either:\n
- save them all to somewhere in your PATH,
- or save them to a directory, then create symlinks to kubectx/kubens from
  \nsomewhere in your PATH, like /usr/local/bin
\n
Make kubectx and kubens executable (chmod +x ...)

\n

Example installation steps:

\n

sudo git clone https://github.com/ahmetb/kubectx /opt/kubectx\nsudo ln -s /opt/kubectx/kubectx /usr/local/bin/kubectx\nsudo ln -s /opt/kubectx/kubens /usr/local/bin/kubens

\n

If you also want to have shell completions, pick an installation method for the
\ncompletion scripts that fits your system best: zsh with
\nantibody, plain
\nzsh,
\nbash or
\nfish.

\n

Completion scripts for `zsh` with antibody

\n

Add this line to your Plugins File (e.g.
\n~/.zsh_plugins.txt):

\n

ahmetb/kubectx path:completion kind:fpath\n

\n

Depending on your setup, you might or might not need to call compinit or
\nautoload -U compinit && compinit in your ~/.zshrc after you load the Plugins
\nfile. If you use oh-my-zsh, load the
\ncompletions before you load oh-my-zsh because oh-my-zsh will call
\ncompinit.

\n

Completion scripts for plain `zsh`

\n

The completion scripts have to be in a path that belongs to $fpath. Either
\nlink or copy them to an existing folder.

\n

Example with oh-my-zsh:

\n

mkdir -p ~/.oh-my-zsh/custom/completions\nchmod -R 755 ~/.oh-my-zsh/custom/completions\nln -s /opt/kubectx/completion/_kubectx.zsh ~/.oh-my-zsh/custom/completions/_kubectx.zsh\nln -s /opt/kubectx/completion/_kubens.zsh ~/.oh-my-zsh/custom/completions/_kubens.zsh\necho \"fpath=($ZSH/custom/completions $fpath)\" >> ~/.zshrc

\n

If completion doesn't work, add autoload -U compinit && compinit to your
\n.zshrc (similar to
\nzsh-completions).

\n

If you are not using oh-my-zsh, you
\ncould link to /usr/share/zsh/functions/Completion (might require sudo),
\ndepending on the $fpath of your zsh installation.

\n

In case of errors, calling compaudit might help.

\n

Completion scripts for `bash`

\n

git clone https://github.com/ahmetb/kubectx.git ~/.kubectx\nCOMPDIR=$(pkg-config --variable=completionsdir bash-completion)\nln -sf ~/.kubectx/completion/kubens.bash $COMPDIR/kubens\nln -sf ~/.kubectx/completion/kubectx.bash $COMPDIR/kubectx\ncat << EOF >> ~/.bashrc\n\n\n#kubectx and kubens\nexport PATH=~/.kubectx:\\$PATH\nEOF

\n

Completion scripts for `fish`

\n

mkdir -p ~/.config/fish/completions\nln -s /opt/kubectx/completion/kubectx.fish ~/.config/fish/completions/\nln -s /opt/kubectx/completion/kubens.fish ~/.config/fish/completions/

\n

\n

Interactive mode

\n

If you want kubectx and kubens commands to present you an interactive menu
\nwith fuzzy searching, you just need to install
\nfzf in your $PATH.

\n

\n

If you have fzf installed, but want to opt out of using this feature, set the
\nenvironment variable KUBECTX_IGNORE_FZF=1.

\n

If you want to keep fzf interactive mode but need the default behavior of the
\ncommand, you can do it by piping the output to another command (e.g. kubectx | cat ).

\n

\n

Customizing colors

\n

If you like to customize the colors indicating the current namespace or context,
\nset the environment variables KUBECTX_CURRENT_FGCOLOR and
\nKUBECTX_CURRENT_BGCOLOR (refer color codes
\nhere):

\n

export KUBECTX_CURRENT_FGCOLOR=$(tput setaf 6) # blue text\nexport KUBECTX_CURRENT_BGCOLOR=$(tput setab 7) # white background

\n

Colors in the output can be disabled by setting the
\nNO_COLOR environment variable.

\n

\n

If you liked kubectx, you may like my
\nkubectl-aliases project, too. I
\nrecommend pairing kubectx and kubens with fzf and
\nkube-ps1.

\n

Stargazers over time

\n

$\"Stargazers$
\n $\"Google$

","updatedAt":"2025-05-21T16:07:43Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"K8S-Tools","color":"2d411a"}},{"node":{"name":"ahmetb","color":"f1e0dc"}}]},"comments":{"edges":[]}}},"pageContext":{"number":312,"previous":{"title":"itaysk/kubectl-neat: 能够智能清除 kubectl get pod -o yaml 时的无用输出，使其更易于阅读","number":311},"next":{"title":"kubecube-io/KubeCube: K8s 资源可视化管理以及统一的多集群多租户管理平台","number":313}}}, "staticQueryHashes": ["151096407","2861350382"]}