Why namespaces provide isolation in Kubernetes - Why It Works

Introduction

When you run many applications in Kubernetes, they can get mixed up and interfere with each other. Namespaces help by creating separate spaces inside the cluster so apps stay apart and don't cause problems.

When you want to run multiple teams' apps on the same Kubernetes cluster without mixing their resources.

When you need to separate development, testing, and production environments inside one cluster.

When you want to limit resource usage and access for different projects or users.

When you want to organize cluster resources logically for easier management.

When you want to apply different security rules to different groups of apps.

Commands

This command creates a new namespace called 'dev-team' to isolate resources for the development team.

Terminal

kubectl create namespace dev-team

Expected Output

namespace/dev-team created

This command lists all namespaces in the cluster so you can see the new 'dev-team' namespace.

Terminal

kubectl get namespaces

Expected Output

NAME              STATUS   AGE

default           Active   10d

kube-system       Active   10d

kube-public       Active   10d

dev-team          Active   1s

This command runs an nginx pod inside the 'dev-team' namespace, keeping it isolated from other namespaces.

Terminal

kubectl run nginx --image=nginx --namespace=dev-team

Expected Output

pod/nginx created

→

--namespace - Specifies the namespace where the pod will be created

This command shows pods running only in the 'dev-team' namespace to verify isolation.

Terminal

kubectl get pods --namespace=dev-team

Expected Output

NAME    READY   STATUS    RESTARTS   AGE

nginx   1/1     Running   0          5s

→

--namespace - Filters pods by the specified namespace

Key Concept

Namespaces create separate spaces inside a Kubernetes cluster so resources and apps do not mix or interfere with each other.

Common Mistakes

Not specifying the namespace when creating or managing resources

Resources get created in the default namespace, causing confusion and mixing with other apps.

Always use the --namespace flag or set the context to the correct namespace before running commands.

Assuming namespaces provide full security isolation

Namespaces isolate resources logically but do not enforce strict security boundaries by themselves.

Use namespaces together with Role-Based Access Control (RBAC) and network policies for proper security.

Summary

Namespaces separate resources inside a Kubernetes cluster to avoid conflicts.

Use 'kubectl create namespace' to make a new isolated space.

Specify the namespace when creating or viewing resources to keep them organized.