When you run a kubectl command, it looks at the to decide where to send the request.

: The default namespace assigned to this context. If empty, it defaults to default . Filtering and Advanced Listing

: The user credentials (e.g., certificates or tokens) used for that cluster.

kubectl config delete-context <context-name>

kubectl config get-contexts

kubectl config get-contexts -o yaml

contexts: - context: cluster: prod-server namespace: production user: prod-user name: prod-cluster - context: cluster: dev-server namespace: development user: dev-user name: dev-cluster current-context: dev-cluster

-n repeatedly. vCluster +7 Workflow Commands To effectively manage these contexts, you'll typically use these related commands: Action Command Purpose List All kubectl config get-contexts View all available environments. Check Active kubectl config current-context Output only the name of the current cluster. Switch kubectl config use-context Instantly change your active target. Set Namespace kubectl config set-context --current --namespace= Update the default namespace for your current session. Community Perspectives While the built-in commands are universally available, many users find the manual typing of long context names to be a bottleneck in complex workflows. Plural.sh “While these built-in commands are reliable... they can feel clunky when you're frequently switching between dozens of clusters.” kubectl list contexts: Manage Kubernetes Clusters - Plural.sh Plural.sh