Diegolden

Topic 3: Pod Security

2 min read

Topic 3: Pod Security

Official baseline: (The Kubernetes Authors, 2026b, 2026a). My working version: Pod security controls the shape of workloads before they run: privilege, host access, users, capabilities, and filesystem behavior.

Mental Model

Pod security controls the shape of workloads before they run: privilege, host access, users, capabilities, and filesystem behavior.

Notes

  • Privileged Pods are a cluster-level decision.
  • Pod Security Standards provide shared vocabulary: privileged, baseline, restricted.
  • Admission can enforce or warn before risky workloads land.

Homelab Angle

Run personal apps under restricted assumptions first, then document exceptions.

Verify It

  • Read the object status before changing the manifest.
  • Check events for the controller or node that is actually complaining.
  • Confirm the official source linked below still matches the cluster version you run.

Common Failure Modes

  • Treating the YAML object as the system, instead of one input to a reconciliation loop.
  • Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
  • Forgetting that Kubernetes version, addon version, and runtime behavior are linked.

Sources

  • Pod Security Standards - source path: content/en/docs/concepts/security/pod-security-standards.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Pod Security Admission - source path: content/en/docs/concepts/security/pod-security-admission.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.
The Kubernetes Authors. (2026a). Pod Security Admission. https://kubernetes.io/docs/concepts/security/pod-security-admission/
The Kubernetes Authors. (2026b). Pod Security Standards. https://kubernetes.io/docs/concepts/security/pod-security-standards/

Graph View

Backlinks