CURRENT NAME CLUSTER AUTHINFO minikube minikube minikube * prod-dallas prod-cluster-dallas admin-prod staging-eu staging-cluster-eu deployer legacy-bare-metal legacy-cluster old-admin The asterisk told him he was currently pointing at . His heart rate doubled. That was production . Live traffic. Real money. Customers ordering cat-shaped planters at 2 AM.
kubectl get context But it didn’t work. The terminal spat back: error: unknown command "get context" - did you mean "config get-contexts"? Right. He’d misremembered. He corrected it: kubectl get context
Vlad opened his terminal, cracked his knuckles, and typed the command every beginner learns first: CURRENT NAME CLUSTER AUTHINFO minikube minikube minikube *
kubectl config use-context staging-eu Switched to context "staging-eu". He applied the fix. It worked perfectly. Then, with a deep breath, he switched back: cracked his knuckles