Kubectl Set-context -

Before diving into the command, it is vital to define what a "context" actually is. In the world of Kubernetes, a context is a bundle of three parameters:

Automating CI/CD PipelinesIn modern CI/CD workflows, such as GitHub Actions, the kubectl-set-context action is frequently used to inject credentials securely (CSDN). This ensures that the runner has the correct access parameters before executing a kubectl apply. Set-Context vs. Use-Context: What’s the Difference?

Result: Every time you switch to the dev-cluster context, your commands will default to the production namespace.

kubectl delete-context dev

Check your current namespace:

# Create a new context linking a specific user to a specific cluster kubectl config set-context new-exp-context --cluster=exp-cluster --user=exp-user

Output:

# Add to ~/.bashrc or ~/.zshrc alias kctx='kubectl config current-context' alias kns='kubectl config view --minify -o jsonpath="..namespace"'

Let's break down each flag:

To delete the "dev" context: