Kubectl Get Context | Verified

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

kubectl config get-contexts The output appeared like a cryptic map: kubectl get context

Carefully, he switched to the staging environment: That was production

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. Customers ordering cat-shaped planters at 2 AM

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.