kubectx — Fast Kubernetes Context & Namespace Switching

What it is

kubectx is a pair of CLI tools (kubectx for cluster contexts, kubens for namespaces) that simplify switching between Kubernetes clusters and namespaces. Instead of typing kubectl config use-context my-long-cluster-name, you type kubectx my-cluster. Tab completion and fuzzy matching make navigation even faster across many clusters.

DevOps engineers and developers working with multiple Kubernetes clusters benefit most from kubectx. If you manage staging, production, and development clusters, kubectx eliminates the friction of context switching.

How it saves time or tokens

kubectx saves seconds on every context switch, which adds up to minutes per day for multi-cluster operators. The previous context shortcut (kubectx -) lets you toggle between two clusters like cd - in a shell. kubens provides the same speed for namespace switching, avoiding the verbose kubectl config set-context commands.

How to use

1. Install kubectx via Homebrew or download the script
2. Run kubectx to list contexts or kubectx <name> to switch
3. Run kubens to list namespaces or kubens <name> to switch

Example

# Install
brew install kubectx

# List all contexts
kubectx
# Output: dev-cluster, staging-cluster, prod-cluster

# Switch context
kubectx prod-cluster
# Switched to context 'prod-cluster'

# Switch back to previous
kubectx -
# Switched to context 'dev-cluster'

# Switch namespace
kubens monitoring
# Context 'dev-cluster' set to namespace 'monitoring'

# Interactive fuzzy selection (with fzf)
kubectx  # launches fzf picker if installed

Related on TokRepo

• DevOps tools — Browse Kubernetes and infrastructure tools
• Featured workflows — Discover top-rated workflows

Common pitfalls

• kubectx modifies your kubeconfig context; running commands in another terminal will use the switched context too
• Renaming contexts with kubectx new=old is convenient but can confuse automation that relies on original names
• kubens only works within the current context; switch context first if you need a different cluster's namespace