Why namespaces provide isolation in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new namespace named 'dev'.

Kubernetes

kubectl create namespace [1]

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

Atest

Bproduction

Cdefault

Ddev

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' instead of 'dev' creates the default namespace, not a new one.

The command kubectl create namespace dev creates a new namespace called 'dev'.

2fill in blank

medium

Complete the command to list all namespaces in the cluster.

Kubernetes

kubectl get [1]

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

Anamespaces

Bpods

Cservices

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' lists pods, not namespaces.

The command kubectl get namespaces lists all namespaces in the cluster.

3fill in blank

hard

Fix the error in the command to delete the 'test' namespace.

Kubernetes

kubectl delete [1] test

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

Anode

Bnamespace

Cservice

Dpod

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pod' deletes a pod, not the namespace.

To delete a namespace, use kubectl delete namespace test. Using 'pod' or others will delete wrong resources or cause errors.

4fill in blank

hard

Fill both blanks to run a pod named 'web' in the 'prod' namespace.

Kubernetes

kubectl run web --image=nginx --namespace=[1] --restart=[2]

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

Aprod

BNever

CAlways

Ddev

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'dev' namespace instead of 'prod'.

Using 'Always' restart policy creates a Deployment, not a pod.

The command kubectl run web --image=nginx --namespace=prod --restart=Never creates a pod named 'web' in the 'prod' namespace.

5fill in blank

hard

Fill all three blanks to create a resource quota named 'quota1' in namespace 'test' limiting pods to 5.

Kubernetes

kubectl create quota [1] --namespace=[2] --hard=[3]

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

Aquota1

Btest

Cpods=5

Dpods=10

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods=10' sets a higher limit than asked.

Wrong namespace name causes quota to apply elsewhere.

This command creates a resource quota named 'quota1' in the 'test' namespace limiting pods to 5.

Practice

1. What is the main reason Kubernetes uses namespaces?

easy

A. To increase the speed of the cluster

B. To reduce the number of nodes in the cluster

C. To isolate resources and avoid conflicts between teams

D. To automatically update all pods

Solution

1. Step 1: Understand the purpose of namespaces

   Namespaces group resources logically to separate them within the same cluster.

2. Step 2: Identify the benefit of isolation

   This separation prevents resource conflicts and allows different teams or projects to work independently.

3. Final Answer:

   To isolate resources and avoid conflicts between teams -> Option C

4. Quick Check:

   Namespaces provide isolation [OK]

Hint: Namespaces separate resources to avoid conflicts [OK]

Common Mistakes:

• Thinking namespaces speed up the cluster
• Confusing namespaces with node management
• Believing namespaces auto-update pods

2. Which of the following is the correct command to list all namespaces in a Kubernetes cluster?

easy

A. kubectl get namespaces

B. kubectl list namespaces

C. kubectl show namespaces

D. kubectl describe namespaces

Solution

1. Step 1: Recall the kubectl command syntax

   The command to list resources uses 'kubectl get' followed by the resource type.

2. Step 2: Identify the correct resource name

   Namespaces are listed with 'kubectl get namespaces'. Other options are invalid commands or show details.

3. Final Answer:

   kubectl get namespaces -> Option A

4. Quick Check:

   List namespaces = kubectl get namespaces [OK]

Hint: Use 'kubectl get namespaces' to list all namespaces [OK]

Common Mistakes:

• Using 'kubectl list' which is not a valid command
• Confusing 'describe' with 'get' for listing
• Using 'show' which is not a kubectl command

3. Given two pods named pod-a in namespaces dev and prod, what happens when you run kubectl get pods -n dev?

medium

A. It shows an error because pod names must be unique cluster-wide

B. It lists only the pod named pod-a in the dev namespace

C. It lists only pods in the prod namespace

D. It lists pods from both dev and prod namespaces

Solution

1. Step 1: Understand namespace scoping of pods

   Pods with the same name can exist in different namespaces without conflict.

2. Step 2: Analyze the command effect

   The command kubectl get pods -n dev lists pods only in the 'dev' namespace.

3. Final Answer:

   It lists only the pod named pod-a in the dev namespace -> Option B

4. Quick Check:

   Namespace limits pod listing [OK]

Hint: Pods with same name can exist in different namespaces [OK]

Common Mistakes:

• Assuming pod names must be unique across cluster
• Expecting pods from all namespaces without -n flag
• Thinking the command lists prod namespace pods

4. You created a pod in namespace test but get an error when trying to access it with kubectl get pod mypod. What is the likely issue?

medium

A. You forgot to specify the namespace with -n test

B. The pod name is invalid

C. The pod does not exist in any namespace

D. kubectl cannot access pods directly

Solution

1. Step 1: Understand default namespace behavior

   Without specifying -n, kubectl uses the default namespace.

2. Step 2: Identify the cause of the error

   If the pod is in test namespace, you must specify -n test to access it.

3. Final Answer:

   You forgot to specify the namespace with -n test -> Option A

4. Quick Check:

   Missing namespace flag causes access error [OK]

Hint: Always specify namespace with -n if not default [OK]

Common Mistakes:

• Assuming pod name is invalid without checking namespace
• Thinking pod does not exist anywhere
• Believing kubectl cannot access pods directly

5. You want to run two versions of the same application in one Kubernetes cluster without conflicts. How do namespaces help achieve this?

hard

A. By restricting access to only one namespace at a time

B. By merging all resources into one namespace automatically

C. By duplicating pods across namespaces without isolation

D. By isolating each version's resources in separate namespaces

Solution

1. Step 1: Understand resource isolation with namespaces

   Namespaces allow running multiple sets of resources independently in the same cluster.

2. Step 2: Apply to running multiple app versions

   Placing each app version in its own namespace prevents naming conflicts and resource overlap.

3. Final Answer:

   By isolating each version's resources in separate namespaces -> Option D

4. Quick Check:

   Namespaces isolate resources for multiple app versions [OK]

Hint: Use separate namespaces to isolate app versions [OK]

Common Mistakes:

• Thinking namespaces merge resources automatically
• Believing pods duplicate without isolation
• Confusing access restriction with resource isolation