Context — Kubectl Get

That night, Vlad added a sticky note to his monitor: And from that day on, not once did he deploy staging YAML to prod—or worse, to the do-not-touch cluster that, rumor had it, still ran the original prototype of the cat planter checkout flow from 2018.

kubectl config use-context prod-dallas But instead of applying immediately, he paused. He wrote a tiny bash alias: kubectl get context

kubectl config get-contexts The output appeared like a cryptic map: That night, Vlad added a sticky note to

alias k-get-ctx='kubectl config get-contexts' Then, just before hitting kubectl apply -f payment-fix.yaml , he ran it again. The asterisk still shone beside prod-dallas . Good. No last-minute surprises. The asterisk still shone beside prod-dallas

Vlad opened his terminal, cracked his knuckles, and typed the command every beginner learns first:

His onboarding task was simple: “Roll out the fix for the payment service.”

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: