Kubectl Change Context ((full)) May 2026
You’ve just been bitten by the .
The kubectl Context Shuffle: How to Stop Breaking Production (and Your Sanity)
kubectl config current-context This tells you the active cluster. I have this aliased in my .zshrc : kubectl change context
kubectl config use-context <context-name> For example:
But wait. That’s the production cluster name in the prompt. Your stomach drops. You just deployed a half-baked, debug-logging, "staging-only" image to the live environment. You’ve just been bitten by the
Mastering the art of kubectl config use-context before you accidentally deploy your test app to the live cluster. Let me paint a picture. It’s 3:00 PM on a Tuesday. You’ve been debugging a tricky authentication bug in your staging environment for two hours. You finally fix it. You type kubectl apply -f deployment.yaml and hit Enter.
kubectl config use-context prod-eks-cluster Output: Switched to context "prod-eks-cluster". Boom. You’re now aiming every kubectl get pods , kubectl logs , and kubectl delete at production. The Pro Move: Know Your Battlefield Before you switch, always check where you are right now . Run: That’s the production cluster name in the prompt
alias kctx='kubectl config current-context' But the real power move is seeing everything you can switch to:
×
