Kubernetes Practical By Samson Tanimawo, PhD Published Feb 6, 2026 4 min read

Namespace Naming Discipline

Namespaces accumulate. The discipline.

Naming convention

Pattern: team-purpose-env. Examples: data-pipelines-prod, platform-monitoring-shared, frontend-app-staging.

Predictable; greppable. Engineers find their namespace without lookup; CI scripts target by pattern.

Avoid generic names like default, kube-system overlap, or single-team brand names that drift.

Required labels on every namespace: team, owner, contact, lifecycle. Documented in metadata; queryable.

Empty ownership is operational debt. Quarterly audit surfaces orphan namespaces; either claimed or retired.

Lifecycle: long-running, ephemeral, batch. Drives cleanup and capacity planning.

Default-deny NetworkPolicy. Namespaces talk only to declared destinations.

Resource quotas per namespace. Single namespace cannot exhaust the cluster.

RBAC scoped to namespace. Cross-namespace access requires explicit permission.

Empty namespaces older than 30 days flagged. Either documented as needed or deleted.

Quarterly review: drift from naming convention, missing labels, orphaned resources.

Retire ephemeral namespaces aggressively. Lifecycle: ephemeral with TTL labels for auto-cleanup.