Switching namespace context in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to switch the current namespace context in kubectl.

Kubernetes

kubectl config set-context --current --namespace=[1]

Drag options to blanks, or click blank then click option'

Aconfig

Bcontext

Cproduction

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'config' or 'context' as namespace names, which are invalid.

The command sets the current context's namespace to the specified one, here 'production'.

2fill in blank

medium

Complete the command to view the current namespace in kubectl context.

Kubernetes

kubectl config view --minify [1]

Drag options to blanks, or click blank then click option'

A-A

B-o jsonpath='{.contexts[0].context.namespace}'

C-o yaml

D-v

Attempts:

3 left

💡 Hint

Common Mistakes

Using grep without proper output formatting, causing no output.

This command extracts the current namespace from the kubectl config using jsonpath.

3fill in blank

hard

Fix the error in the command to switch namespace context.

Kubernetes

kubectl config set-context [1] --namespace=staging

Drag options to blanks, or click blank then click option'

A--current

Bcurrent

C--context

Dcontext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'current' without dashes or '--context' which changes a named context.

The correct flag to modify the current context is '--current'.

4fill in blank

hard

Fill both blanks to create a command that switches to the 'dev' namespace and then lists pods.

Kubernetes

kubectl config set-context [1] --namespace=[2] && kubectl get pods

Drag options to blanks, or click blank then click option'

A--current

Bdev

Cdefault

D--namespace

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--namespace' as the first blank or 'default' instead of 'dev'.

Use '--current' to modify the current context and 'dev' as the namespace name.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps pod names to their statuses for pods in the current namespace.

Kubernetes

pods_status = { [1]: [2].status.phase for [3] in pods.items() }

Drag options to blanks, or click blank then click option'

Apod.metadata.name

Bpod

D{

Attempts:

3 left

💡 Hint

Common Mistakes

Not starting with '{', or using wrong variable names.

The dictionary comprehension {pod.metadata.name: pod.status.phase for pod in pods.items()} maps pod names to their status phases.

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