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

Need a 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

Need a 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

Need a 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

Need a hint?

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