Switching namespace context in Kubernetes - Commands & Configuration

Introduction

Kubernetes organizes resources into namespaces to keep things separate. Switching namespace context lets you work in a specific namespace without typing it every time.

When you have multiple projects running in the same Kubernetes cluster and want to focus on one project.

When you want to avoid typing --namespace flag repeatedly for commands.

When you need to check resources like pods or services in a specific namespace quickly.

When you are troubleshooting issues isolated to one namespace.

When you want to create or delete resources only in a particular namespace.

Commands

This command lists all available contexts and shows the current namespace for each. It helps you see what namespaces you can switch to.

Terminal

kubectl config get-contexts

Expected Output

CURRENT   NAME                 CLUSTER          AUTHINFO         NAMESPACE

*         my-cluster-context   my-cluster       [e-mail]  default

This command changes the current context's namespace to 'example-namespace'. After this, kubectl commands run in this namespace by default.

Terminal

kubectl config set-context --current --namespace=example-namespace

Expected Output

Context "my-cluster-context" modified.

→

--current - Modifies the current active context

→

--namespace - Sets the default namespace for the context

This command lists pods in the current namespace, which is now 'example-namespace'. It verifies that the namespace switch worked.

Terminal

kubectl get pods

Expected Output

NAME                     READY   STATUS    RESTARTS   AGE

my-app-pod-1234567890    1/1     Running   0          10m

This command shows the namespace currently set in the active context to confirm the switch.

Terminal

kubectl config view --minify | grep namespace:

Expected Output

    namespace: example-namespace

→

--minify - Shows only the current context details

Key Concept

If you remember nothing else from this pattern, remember: setting the namespace in your current context saves you from typing --namespace every time.

Common Mistakes

Trying to switch namespace by running 'kubectl config set-context' without the --current flag.

This creates or modifies a context but does not change the active context's namespace, so your commands still run in the old namespace.

Always use '--current' to change the namespace of the active context.

Assuming 'kubectl get pods' shows pods from all namespaces after switching context namespace.

kubectl commands without --all-namespaces flag only show resources in the current namespace.

Use 'kubectl get pods --all-namespaces' to see pods across all namespaces.

Summary

Use 'kubectl config set-context --current --namespace=your-namespace' to switch your default namespace.

Verify the switch by running 'kubectl get pods' to see resources in the new namespace.

Check the current namespace with 'kubectl config view --minify | grep namespace:'.

Practice

1. What does switching the namespace context in Kubernetes help you do?

easy

A. Work easily within a specific namespace without typing it every time

B. Delete all namespaces at once

C. Create a new Kubernetes cluster

D. Change the Kubernetes version

Solution

1. Step 1: Understand namespaces in Kubernetes

   Namespaces organize resources so you can separate projects or teams.

2. Step 2: Understand switching namespace context

   Switching context means your commands default to that namespace, so you don't type it each time.

3. Final Answer:

   Work easily within a specific namespace without typing it every time -> Option A

4. Quick Check:

   Switching namespace context = easier work in one namespace [OK]

Hint: Switching namespace saves typing namespace each command [OK]

Common Mistakes:

• Thinking switching namespace deletes namespaces
• Confusing namespace with cluster creation
• Believing it changes Kubernetes version

2. Which of the following is the correct command to switch the current namespace to dev?

easy

A. kubectl set namespace dev

B. kubectl config set-context --current --namespace=dev

C. kubectl switch namespace dev

D. kubectl change context namespace dev

Solution

1. Step 1: Recall the correct syntax for switching namespace context

   The command uses kubectl config set-context --current --namespace=<name>.

2. Step 2: Match the command with the namespace dev

   Replace <name> with dev exactly as in kubectl config set-context --current --namespace=dev.

3. Final Answer:

   kubectl config set-context --current --namespace=dev -> Option B

4. Quick Check:

   Correct syntax = kubectl config set-context --current --namespace=dev [OK]

Hint: Use 'kubectl config set-context --current --namespace=' [OK]

Common Mistakes:

• Using non-existent commands like 'kubectl switch namespace'
• Omitting '--current' flag
• Using wrong command verbs like 'change' or 'set' alone

3. What will be the output of the command kubectl config view --minify | grep namespace after running kubectl config set-context --current --namespace=testing?

medium

A. namespace: default

B. Error: namespace not found

C. No output

D. namespace: testing

Solution

1. Step 1: Understand what kubectl config set-context --current --namespace=testing does

   This command sets the current context's namespace to testing.

2. Step 2: Understand the kubectl config view --minify | grep namespace command

   This shows the current context's namespace setting, which should now be testing.

3. Final Answer:

   namespace: testing -> Option D

4. Quick Check:

   Namespace after set-context = testing [OK]

Hint: Check current namespace with 'kubectl config view --minify' [OK]

Common Mistakes:

• Expecting default namespace after switching
• Thinking command shows all namespaces
• Assuming error if namespace does not exist yet

4. You ran kubectl config set-context --current --namespace=prod but your commands still affect the default namespace. What is the likely problem?

medium

A. You did not reload your shell or terminal

B. You used the wrong command to switch namespace

C. Your current context is not set correctly

D. The namespace prod does not exist

Solution

1. Step 1: Check if the current context is set correctly

   If the current context is not the one you expect, switching namespace won't affect your commands.

2. Step 2: Understand that namespace switching affects only the current context

   Switching namespace changes the namespace in the current context, so if the context is wrong, commands still use default namespace.

3. Final Answer:

   Your current context is not set correctly -> Option C

4. Quick Check:

   Namespace switch affects current context only [OK]

Hint: Verify current context with 'kubectl config current-context' [OK]

Common Mistakes:

• Assuming shell reload is needed
• Thinking namespace must exist before switching
• Using wrong command syntax

5. You want to run multiple commands in the staging namespace without typing --namespace=staging each time. Which sequence of commands correctly sets this up and verifies it?

hard

A. kubectl config set-context --current --namespace=staging
kubectl get pods
kubectl config view --minify | grep namespace

B. kubectl namespace staging
kubectl get pods
kubectl config current-context

C. kubectl switch namespace staging
kubectl get pods
kubectl config get-contexts

D. kubectl set namespace staging
kubectl get pods
kubectl config get-namespaces

Solution

1. Step 1: Set the current context's namespace to staging

   Use kubectl config set-context --current --namespace=staging to switch namespace context.

2. Step 2: Verify by listing pods and checking namespace in current context

   Running kubectl get pods uses the new namespace by default. Checking with kubectl config view --minify | grep namespace confirms the namespace is set.

3. Final Answer:

   kubectl config set-context --current --namespace=staging kubectl get pods kubectl config view --minify | grep namespace -> Option A

4. Quick Check:

   Set context namespace then verify with config view [OK]

Hint: Set namespace once with config set-context, then run commands [OK]

Common Mistakes:

• Using non-existent commands like 'kubectl switch namespace'
• Not verifying namespace change
• Confusing context commands with namespace commands