TOPIC CONTAINERS
Namespaces & Multi-tenancy many teams, one cluster
IN 10 SECONDS
Kubernetes Namespaces partition a single physical cluster into multiple virtual clusters, allowing teams to share compute resources without interfering with each other's configuration.
GOTCHA Namespaces do not isolate networking. By default, pods in namespace-a can communicate with pods in namespace-b unless you block them with NetworkPolicies.
HOW NAMESPACE ISOLATION WORKS
01 Request division administrator creates two namespaces: team-a and team-b.
02 RBAC assign assigns permissions restricting developers to their respective namespaces.
03 Quota limit allocates CPU/Memory caps per namespace to prevent resource hogging.
04 DNS Routing service names resolve locally (my-svc) or across namespaces (my-svc.team-a.svc.cluster.local).
POKE IT YOURSELF
kubectl get ns — list all namespaces in the cluster
kubectl create ns test-env — create a new namespace
Drill this topic →
~70 sec read