Kubectl Config Set Context -

We have all been there.

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

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

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. Use Case 2: The "Quick Fix" (Modifying the