Why namespaces provide isolation in Kubernetes - See It in Action

Why namespaces provide isolation

📖 Scenario: You are managing a Kubernetes cluster shared by multiple teams. Each team needs its own space to deploy applications without interfering with others.

🎯 Goal: Learn how to create Kubernetes namespaces and understand how they isolate resources within the cluster.

📋 What You'll Learn

Create a Kubernetes namespace called team-a

Create a Kubernetes namespace called team-b

Deploy a simple pod in the team-a namespace

Deploy a simple pod in the team-b namespace

Verify pods are isolated by namespaces

💡 Why This Matters

🌍 Real World

In real companies, multiple teams share Kubernetes clusters. Namespaces keep their apps separate and safe.

💼 Career

Understanding namespaces is key for Kubernetes administrators and DevOps engineers to manage multi-team environments.

1

Create the team-a namespace

Write the command to create a Kubernetes namespace called team-a.

Kubernetes

# Your code here

Hint

Use kubectl create namespace followed by the namespace name.

2

Create the team-b namespace

Write the command to create a Kubernetes namespace called team-b.

Kubernetes

kubectl create namespace team-a
# Your code here

Hint

Repeat the namespace creation command with the new name team-b.

3

Deploy a pod in the team-a namespace

Write the command to run a pod named pod-a using the nginx image in the team-a namespace.

Kubernetes

kubectl create namespace team-a
kubectl create namespace team-b
# Your code here

Hint

Use kubectl run with --namespace=team-a to deploy the pod in the correct namespace.

4

Deploy a pod in the team-b namespace and verify isolation

Write the command to run a pod named pod-b using the nginx image in the team-b namespace. Then write the command to list pods in the team-a namespace and the team-b namespace separately.

Kubernetes

kubectl create namespace team-a
kubectl create namespace team-b
kubectl run pod-a --image=nginx --namespace=team-a
# Your code here

Hint

Deploy the pod in team-b namespace and use kubectl get pods --namespace=... to see pods in each namespace.

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