The danger isn't malice; it’s . You forget to switch contexts like you forget to un-mute your mic in a meeting. And the consequences range from "oops, I restarted the wrong dashboard" to "why is QA testing my half-written feature?" The Hero Command: kubectl config use-context The fix is simple, fast, and boring—which is exactly what you want from an infrastructure tool.
So if you find yourself constantly typing -n my-namespace after every command, bake it into the context itself. kubectl change context
The terminal blinks. Then it whispers back: "deployment.apps/payment-gateway created." The danger isn't malice; it’s
kubectl config current-context This tells you the active cluster. I have this aliased in my .zshrc : So if you find yourself constantly typing -n
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.
kubectl config use-context <context-name> For example:
Now go forth, switch safely, and may your deployments always land where you intend. Have a "wrong context" horror story? Or a clever alias that saves you daily? Drop it in the comments—misery loves company.