For example, create a context for production that automatically sets a strict namespace, but combine it with a shell prompt change.
Because in the world of distributed systems, the most important cluster to control isn't the one in the cloud—it's the one inside your terminal.
Master this command. Alias it. Love it.
Finally, he ran kubectl config get-contexts . He was in cluster-2 (staging) but his mind was in cluster-1 (production). The pod was running perfectly. He was just looking at the wrong wall.
get_k8s_context() { echo "$(kubectl config current-context 2>/dev/null)" } PROMPT='$(get_k8s_context) $ ' kubectl config set context
We have all been there.
The root cause is almost always the same: Context blindness. You were looking at the wrong cluster or the wrong namespace. Enter the most underrated lifesaver in the Kubernetes CLI toolbox: . For example, create a context for production that
kubectl config set-context prod-payment \ --cluster=prod-us-east \ --user=prod-admin \ --namespace=payment kubectl creates a new context entry named prod-payment in your kubeconfig. It does not switch to it yet (for that, you need kubectl config use-context ). Use Case 2: The "Quick Fix" (Modifying the Current Context) This is where the magic happens for daily operations. Let's say you are currently in the frontend namespace, but you need to run a database migration in the db-migration namespace. You don't want to create a permanent new context.