Diegolden

Security And Policy

1 min read

Security And Policy

Kubernetes security is layered. No single object makes the cluster safe.

Topics

  • API Access Control - Every meaningful Kubernetes action becomes an API request that must authenticate, authorize, and pass admission.
  • Service Accounts And RBAC - Service accounts are workload identities. RBAC defines what those identities can do.
  • Pod Security - Pod security controls the shape of workloads before they run: privilege, host access, users, capabilities, and filesystem behavior.
  • Admission And Policy - Admission is the gate between a valid API request and a request the cluster should actually accept.
  • Secret Handling - Secret handling is a full lifecycle: creation, storage, access, rotation, exposure, and deletion.

Editorial Notes

  • Keep the official docs as the citation layer.
  • Keep this lab opinionated around homelab operations: verification, failure modes, and practical boundaries.
  • Avoid copying upstream prose; cite it, then explain the operating model in our own language.

Sources

  • Security - source path: content/en/docs/concepts/security/_index.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Controlling Access to the Kubernetes API - source path: content/en/docs/concepts/security/controlling-access.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Pod Security Standards - source path: content/en/docs/concepts/security/pod-security-standards.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.

5 items under this folder.