Namespace

Namespaces partition cluster resources for teams, environments, or applications. They help apply RBAC, quotas, network policies, naming boundaries, and operational ownership.

					kubectl get all -n staging
kubectl auth can-i create deployment --namespace production
				

Namespaces do not isolate nodes, cluster-scoped resources (PersistentVolumes, StorageClasses, CRDs), or noisy neighbors without additional policies.

On interviews: what namespaces isolate versus what remains shared; multi-tenant risk; when separate clusters beat namespaces.

Common pitfalls: treating a namespace as a security boundary without NetworkPolicy and quotas; one namespace for prod and experiments.

The trade-off is operational simplicity (few namespaces) versus blast-radius control.

Checklist:

• Use namespaces for ownership boundaries.
• Add quotas and network policies.
• Know cluster-scoped resources.
• Escalate to separate clusters when isolation requirements grow.