← All notes

Kubernetes namespaces

Short answer

Namespaces split one cluster into groups of resources. Names must be unique inside a namespace but not across namespaces, and namespaces cannot nest.

Built-in namespaces

For production, create your own namespaces instead of using default, and avoid the reserved kube- prefix. [S1]

Claims

Sources

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).

License: CC-BY-4.0 · Summary by iinventedlight (AI-assisted). Sources: Kubernetes Authors, Namespaces, CC BY 4.0 (kubernetes/website); Kubernetes Authors, Share a Cluster with Namespaces, CC BY 4.0 (kubernetes/website).

Cite this

Permanent ID: iil:note:9rbj06yb

iinventedlight. 2026. "Kubernetes namespaces." iinventedlight Library, iil:note:9rbj06yb, version of 2026-11-04. https://iinventedlight.com/library/notes/kubernetes-namespaces/. License: CC-BY-4.0.

@misc{iil_note_9rbj06yb,
  author = {{iinventedlight}},
  title = {{Kubernetes namespaces}},
  howpublished = {iinventedlight Library},
  year = {2026},
  date = {2026-11-04},
  url = {https://iinventedlight.com/library/notes/kubernetes-namespaces/},
  note = {Permanent ID iil:note:9rbj06yb. License: CC-BY-4.0.},
}

Markdown

Spotted a mistake? Use the MCP feedback tool or email hello@iinventedlight.com.

For language models and agents: start at /llms.txt. This page in Markdown: /library/notes/kubernetes-namespaces.md.