Switching namespace context in Kubernetes - Step-by-Step Execution

Process Flow - Switching namespace context

Start: Current kubectl context

↓

Check current namespace

↓

Run command: kubectl config set-context --current --namespace=<new-namespace>

↓

Update context namespace

↓

Verify with kubectl config view or kubectl config get-contexts

↓

kubectl commands now use new namespace

↓

END

This flow shows how you change the current kubectl namespace context so commands run in the new namespace.

Execution Sample

Kubernetes

kubectl config set-context --current --namespace=dev
kubectl get pods

Switch current kubectl context to 'dev' namespace, then list pods in 'dev' namespace.

Process Table

Step	Command	Context Namespace Before	Action	Context Namespace After	Output
1	kubectl config get-contexts --no-headers -o name	default	Check current context name	default	current-context-name
2	kubectl config view --minify --output 'jsonpath={..namespace}'	default	Check current namespace	default	default
3	kubectl config set-context --current --namespace=dev	default	Set current context namespace to 'dev'	dev	Context updated.
4	kubectl config view --minify --output 'jsonpath={..namespace}'	dev	Verify namespace change	dev	dev
5	kubectl get pods	dev	List pods in new namespace	dev	No resources found in dev namespace.
6	kubectl config set-context --current --namespace=default	dev	Switch back to default namespace	default	Context updated.
7	kubectl get pods	default	List pods in default namespace	default	pod1 pod2 pod3
8	-	default	End of demonstration	default	-

💡 Namespace context switched successfully; kubectl commands now run in the selected namespace.

Status Tracker

Variable	Start	After Step 3	After Step 6	Final
current_namespace	default	dev	default	default

Key Moments - 3 Insights

Why do kubectl commands still show resources from the default namespace before switching?

Because the current context's namespace is 'default' initially (see execution_table step 2), so kubectl commands run in 'default' namespace until changed.

Does 'kubectl config set-context --current --namespace=dev' create the namespace 'dev' if it doesn't exist?

No, it only changes the context's namespace setting. The namespace must exist already or kubectl commands may fail or show no resources (see step 5).

How to verify the namespace context has changed?

Use 'kubectl config view --minify --output jsonpath={..namespace}' as shown in steps 2 and 4 to see the current namespace.

Visual Quiz - 3 Questions

Look at the execution table, what is the namespace after step 3?

A default

B dev

C kube-system

D production

💡 Hint

Check the 'Context Namespace After' column in step 3.

At which step does the kubectl command start listing pods in the 'dev' namespace?

A Step 2

B Step 4

C Step 5

D Step 7

💡 Hint

Look at the 'Command' and 'Output' columns to find when pods are listed in 'dev'.

If you run 'kubectl get pods' without switching namespace, which namespace is used by default?

A default

B dev

C kube-public

D custom

💡 Hint

See the 'Context Namespace Before' in step 1 and 2.

Concept Snapshot

Switch namespace context in kubectl:
- Use: kubectl config set-context --current --namespace=<namespace>
- Changes current context's namespace
- Verify with: kubectl config view --minify --output 'jsonpath={..namespace}'
- Commands like 'kubectl get pods' run in new namespace
- Namespace must exist beforehand

Full Transcript

This lesson shows how to switch the namespace context in kubectl. You start by checking your current namespace, usually 'default'. Then you run 'kubectl config set-context --current --namespace=dev' to change the namespace to 'dev'. After that, kubectl commands like 'kubectl get pods' will operate in the 'dev' namespace. You can verify the change by viewing the current namespace in the context. Switching back to 'default' is done the same way. Remember, changing the context does not create namespaces; they must exist already.