Switching namespace context in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Kubernetes namespace?

A Kubernetes namespace is like a folder that helps organize and separate resources in a cluster. It allows you to group related resources together.

beginner

How do you check the current namespace context in kubectl?

Use the command kubectl config view --minify --output 'jsonpath={..namespace}' to see the current namespace set in your context.

beginner

What command switches the current namespace context to 'dev'?

Run kubectl config set-context --current --namespace=dev to switch your current context to the 'dev' namespace.

beginner

Why is switching namespaces useful in Kubernetes?

Switching namespaces lets you work on different projects or environments without mixing resources. It keeps things organized and safe.

beginner

How to list all namespaces in a Kubernetes cluster?

Use kubectl get namespaces to see all namespaces available in your cluster.

Which command changes your current namespace to 'test'?

A kubectl switch namespace test

B kubectl config set-context --current --namespace=test

C kubectl change namespace test

D kubectl set namespace test

The correct command is kubectl config set-context --current --namespace=test to switch namespace context.

What does a Kubernetes namespace help you do?

A Organize resources into groups

B Increase cluster CPU

C Change pod images

D Delete the cluster

Namespaces help organize and separate resources inside a Kubernetes cluster.

How do you see the current namespace your kubectl is using?

A kubectl get current namespace

B kubectl show namespace

C kubectl namespace current

D kubectl config view --minify --output 'jsonpath={..namespace}'

Use kubectl config view --minify --output 'jsonpath={..namespace}' to check the current namespace.

What happens if you don’t specify a namespace in kubectl commands?

A kubectl uses the default namespace

B kubectl fails with error

C kubectl deletes all namespaces

D kubectl creates a new namespace

If no namespace is specified, kubectl uses the 'default' namespace.

Which command lists all namespaces in your Kubernetes cluster?

A kubectl list namespaces

B kubectl show namespaces

C kubectl get namespaces

D kubectl namespaces list

The command kubectl get namespaces lists all namespaces.

Explain how to switch your current kubectl context to a different namespace and why you might want to do this.

Think about how namespaces separate resources and how kubectl context controls where commands run.

Describe how to check which namespace your kubectl commands are currently using.

Look at the kubectl config and how it shows the active 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