His onboarding task was simple: “Roll out the fix for the payment service.”
It was Vlad’s first day on the job as a platform engineer at a chaotic startup called Nebulous Systems. The previous “kube-whisperer” had left behind a labyrinth of Kubernetes clusters: staging, prod, legacy, and one ominously named “do-not-touch.” kubectl get context
Carefully, he switched to the staging environment: His onboarding task was simple: “Roll out the
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: It worked perfectly
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:
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.
Vlad opened his terminal, cracked his knuckles, and typed the command every beginner learns first: