Pod Security Admission
The built-in Kubernetes admission controller that applies Pod Security Standards to each namespace according to its labels.
In more detail
Each namespace can enforce one level and warn or audit another, pinned to a Kubernetes version so an upgrade cannot tighten rules by surprise. Enforcement checks pods, so a Deployment is accepted and its pods are then refused.
Examples
pod-security.kubernetes.io/enforce: baseline plus pod-security.kubernetes.io/warn: restrictedpod-security.kubernetes.io/enforce: restrictedRelated terms
- Pod Security Standards — Three built-in Kubernetes security profiles, called privileged, baseline and restricted, that define how locked down a pod must be.
- admission controller — A Kubernetes API server plugin that checks or changes each request after authentication and authorization, before the object is stored.
- dry run — Sending a real request in a check-only mode, so the system reports whether it would succeed without actually making the change.
- PodSecurityPolicy — An older Kubernetes pod security mechanism that was removed in version 1.25 and replaced by Pod Security Admission.
Taught in
- Authentication, Authorisation And Admission — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Two Hours, Sixteen Tasks: A CKS Plan — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Seccomp: Which Syscalls A Container May Make — Certified Kubernetes Security Specialist (CKS) Exam Prep
- AppArmor: The Guard Docker Desktop Does Not Have — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Pod Security Admission: Created, Never Started — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Final Review: The Cluster You Would Defend — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Kubernetes Pod Security Standards: Baseline & Restricted — Cloud Security & DevSecOps Engineering
- One Leaked Kubeconfig: How Far Does It Go? — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Ninety Minutes, Six Domains: Where The Marks Are — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Same Rule, Two Kinds: Controls And Frameworks — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Overview Sprint: Four Findings Before The Auditor — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- A Pod That Mounts The Node: Runtime, Pods And Storage — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Component Sprint: The Reference Build — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Created, But Never Running: Pod Security Admission — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Encoded Is Not Hidden: Secrets — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Fundamentals Sprint: Four Findings, Eight Questions — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- What Outlives The Fix: Persistence And Privilege Escalation — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- The Report That Ate The Node: Denial Of Service And Malicious Code — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Pod Away: Network Attackers And Sensitive Data — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Who Built This Image? Supply Chain And Registries — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Forty Three Of Sixty: The Mock, And How To Read It — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Audit Day: Final Review — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- securityContext: Nonroot, Capabilities And Seccomp — Kubernetes: Production-Grade Container Orchestration
- Pod Security Admission And Pod Security Standards — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Forbidden Requests And Admission Rejections — Kubernetes: Production-Grade Container Orchestration