For example, create a context for production that automatically sets a strict namespace, but combine it with a shell prompt change.
kubectl config set-context [NAME] --cluster=[CLUSTER] --user=[USER] --namespace=[NAMESPACE] Imagine you have a production cluster named prod-us-east and a user named prod-admin . You want a quick way to switch to the payment namespace.
We have all been there.
You run kubectl get pods . Everything looks healthy. You scale a deployment. You check the logs. Only then do you realize—you just blew up the staging environment while trying to debug production. Or worse, you deleted a critical configmap from the wrong bank of servers.
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.
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.
Add this to your ~/.zshrc or ~/.bashrc :
For example, create a context for production that automatically sets a strict namespace, but combine it with a shell prompt change.
kubectl config set-context [NAME] --cluster=[CLUSTER] --user=[USER] --namespace=[NAMESPACE] Imagine you have a production cluster named prod-us-east and a user named prod-admin . You want a quick way to switch to the payment namespace.
We have all been there.
You run kubectl get pods . Everything looks healthy. You scale a deployment. You check the logs. Only then do you realize—you just blew up the staging environment while trying to debug production. Or worse, you deleted a critical configmap from the wrong bank of servers.
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. kubectl config set context
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.
Add this to your ~/.zshrc or ~/.bashrc :