Set Context - Kubectl Config

Add this to your ~/.zshrc or ~/.bashrc :

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: . kubectl config set context

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. Add this to your ~/