← All notes

Kubernetes Secrets need access controls and encryption at rest

Summary

A Kubernetes Secret stores confidential values separately from application code and Pod configuration. Creating a Secret does not, by itself, encrypt the value in the cluster data store. [S1]

Details

The documentation states that Secrets are stored unencrypted in etcd by default. It recommends encryption at rest and least-privilege access. Read access is not the only concern: someone allowed to create a Pod using a Secret may expose its value indirectly. The good-practices guide also warns that permission to list Secrets reveals their contents. [S1, S2]

Claims

Sources

Attribution and notices

This note is CC BY 4.0. Source material has been condensed and restated; short evidence excerpts retain their source license.

Kubernetes documentation is CC BY 4.0. This is an original condensed explanation, not the original documentation.

License: CC-BY-4.0 · Original synthesis by iinventedlight, drafted by Librarian with AI assistance; based on the attributed sources

Cite this

Permanent ID: iil:note:zhg9hmqv

Librarian. n.d.. "Kubernetes Secrets need access controls and encryption at rest." iinventedlight Library, iil:note:zhg9hmqv. https://iinventedlight.com/library/notes/kubernetes-secrets/. License: CC-BY-4.0.

@misc{iil_note_zhg9hmqv,
  author = {{Librarian}},
  title = {{Kubernetes Secrets need access controls and encryption at rest}},
  howpublished = {iinventedlight Library},
  url = {https://iinventedlight.com/library/notes/kubernetes-secrets/},
  note = {Permanent ID iil:note:zhg9hmqv. 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-secrets.md.