kubectl config get-contexts -o name Cause : You may have an environment variable $KUBECONFIG pointing to a different file, or you're using a shell alias that hardcodes --context .
kubectl config get-contexts Example output: kubectl change current context
unset KUBECONFIG alias | grep kubectl After switching context, always check your namespace: kubectl config get-contexts -o name Cause : You
| Method | Persistence | Use Case | |--------|-------------|-----------| | kubectl config use-context | Permanent (updates file) | Day-to-day interactive work | | --context flag | One command | Ad-hoc query in another cluster | | $KUBECONFIG_CONTEXT env var | Shell session | Temporary context for a script block | | kubectx | Permanent | Faster, interactive switching | Conclusion The command kubectl config use-context is deceptively simple but profoundly powerful. It is the steering wheel of your Kubernetes command-line interface. Mastering it means moving confidently between environments, reducing costly mistakes (like applying a production manifest to a local cluster), and building muscle memory for safe cluster operations. kubectl change current context
: List available contexts first: