Switching namespace context in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of switching namespace context?

You run the command kubectl config set-context --current --namespace=dev. What will be the output or effect of this command?

A The command outputs 'Switched to namespace dev' and changes the context.

B An error message saying 'namespace dev not found' is displayed.

C The current context's namespace is changed to 'dev' with no output message.

D The current context is deleted and a new context named 'dev' is created.

💡 Hint

Think about what the command does to the current context and if it outputs messages.

The command changes the namespace of the current context silently without output. It does not create or delete contexts or print confirmation messages.

💻 Command Output

intermediate

What happens if you switch to a non-existent namespace?

You run kubectl config set-context --current --namespace=unknown but the namespace 'unknown' does not exist. What is the result?

A The context namespace is set to 'unknown' even if it does not exist, with no error.

B kubectl returns an error: 'namespace unknown not found'.

C The command fails with a syntax error.

D kubectl creates the 'unknown' namespace automatically and switches context.

💡 Hint

Does kubectl validate namespace existence when setting context namespace?

kubectl does not check if the namespace exists when setting the context namespace. It just updates the config.

🔀 Workflow

advanced

Correct sequence to switch namespace context and verify

Arrange the following commands in the correct order to switch the current kubectl context to namespace 'test' and verify the change.

A 1,3,2,4

B 1,4,3,2

C 1,2,4,3

D 4,1,3,2

💡 Hint

First switch namespace, then check pods in that namespace, then verify namespace in context, finally list all namespaces.

You first set the namespace in the current context, then get pods to see resources in that namespace, then verify the namespace setting, and finally list all namespaces.

❓ Troubleshoot

advanced

Why does kubectl still show pods from default namespace after switching?

You ran kubectl config set-context --current --namespace=prod but kubectl get pods still shows pods from the 'default' namespace. What is the most likely cause?

A You did not reload or restart your shell session after switching namespaces.

B You are overriding the namespace with the <code>--namespace</code> flag in your get pods command.

C You have multiple contexts and the current context was not changed.

D The 'prod' namespace does not exist, so kubectl defaults to 'default'.

💡 Hint

Check if any command line flags override the context namespace.

The --namespace flag in kubectl commands overrides the context namespace setting. If you specify --namespace=default, it will show pods from default namespace regardless of context.

✅ Best Practice

expert

Best practice to switch namespace context safely in scripts

You want to write a script that switches the kubectl context namespace to 'staging' only if the namespace exists. Which approach is best?

A Create the namespace with <code>kubectl create namespace staging</code> before switching context.

B Delete the current context and create a new one with namespace 'staging'.

C Directly run <code>kubectl config set-context --current --namespace=staging</code> without checking.

D Run <code>kubectl get namespace staging</code> and if it exists, run <code>kubectl config set-context --current --namespace=staging</code>.

💡 Hint

Think about avoiding errors in scripts by checking resource existence first.

Checking if the namespace exists before switching prevents errors or misconfigurations in scripts. Creating or deleting contexts unnecessarily is not recommended.