Master Fast Kubernetes Cluster Switching with kubectx and kubens

When operating multiple Kubernetes clusters with kubectl, manually renaming config files becomes cumbersome, especially if you frequently switch between environments such as a local Minikube cluster and production clusters.

Kubernetes solves this with contexts in the kubeconfig file, allowing you to define multiple clusters, users, and contexts in a single file.

A common pitfall occurs when two clusters share the same user name and TLS credentials; kubectl may merge the client-certificate-data and client-key-data fields, causing one cluster to become unreachable. The fix is to rename the user field in each context and update the corresponding entry under users so the names match.

apiVersion: v1
kind: Config
preferences: {}
clusters:
- cluster:
    server: https://xxxxx:6443
    certificate-authority-data: xxxxx
  name: cluster1  # first cluster name
- cluster:
    server: https://xxxxx:6443
    certificate-authority-data: xxxxx
  name: cluster2  # second cluster name
contexts:
- context:
    cluster: cluster1
    user: user1
  name: cluster1
- context:
    cluster: cluster2
    user: user2
  name: cluster2
users:
- name: user1
  user:
    client-certificate-data: xxxxxxxxx
    client-key-data: xxxxxxxxxxxxx
- name: user2
  user:
    client-certificate-data: xxxxxxxxx
    client-key-data: xxxxxxxxxxxxx

As long as the clusters , contexts , and users entries have unique names, you can add any number of them.

To switch contexts more conveniently, the open‑source tool kubectx (and its companion kubens for namespaces) can be used.

1. Installation

Clone the repository and copy the binaries to a directory in your PATH. The binaries are renamed to avoid interfering with kubectl auto‑completion.

git clone https://github.com/ahmetb/kubectx
cd kubectx
cp kubectx/kube* /usr/local/bin/
chmod +x /usr/local/bin/kube*
mv /usr/local/bin/kubectx /usr/local/bin/kbx
mv /usr/local/bin/kubens /usr/local/bin/kbs

Renaming prevents the tool from overriding kubectl 's completion scripts.

2. Using kubectx to switch contexts quickly

2.1 Basic usage

kbx -h
USAGE:
  kubectx               : list the contexts
  kubectx <NAME>        : switch to context <NAME>
  kubectx -             : switch to the previous context
  kubectx -c, --current : show the current context name
  kubectx <NEW_NAME>=<NAME> : rename context <NAME> to <NEW_NAME>
  kubectx <NEW_NAME>=. : rename current‑context to <NEW_NAME>
  kubectx -d <NAME> [...] : delete context <NAME>
  kubectx -u, --unset   : unset the current context
  kubectx -h,--help     : show this message

2.2 List all contexts

kbx
cluster1
cluster2

2.3 Switch to a specific context

kbx cluster1
Switched to context "cluster1".

2.4 Switch back to the previous context

kbx -
Switched to context "cluster1".

3. Using kubens to switch namespaces

3.1 Basic usage

kbs -h
USAGE:
  kubens               : list the namespaces in the current context
  kubens <NAME>        : change the active namespace of current context
  kubens -             : switch to the previous namespace in this context
  kubens -c, --current : show the current namespace
  kubens -h,--help     : show this message

3.2 List all namespaces

kbs
default
kube-public
kube-system

3.3 Switch to a specific namespace

kbs kube-system
Context "cluster1" modified.
Active namespace is "kube-system".

⚠️ Managing multiple clusters on the same machine is convenient, but ensure each cluster has distinct permissions and contexts to avoid security issues.