Individual skill
implementing-pod-security-admission-controller
Configures and operates the Kubernetes Pod Security Admission (PSA) controller that enforces Pod Security Standards: namespace enforce/audit/warn labels, cluster-wide defaults via AdmissionConfiguration, exemptions for usernames, runtime classes and namespaces, version pinning, and troubleshooting pods the controller rejected. Use when wiring PSA up on a cluster, setting cluster-wide default enforcement, exempting system namespaces, debugging why a pod was rejected or why enforcement is not firing, or reading PSA audit and warning output. Keywords: Pod Security Admission, PSA, admission controller, AdmissionConfiguration, pod-security.kubernetes.io labels, enforce audit warn, exemptions, kube-apiserver. Do not use for choosing which security profile a workload needs - use implementing-kubernetes-pod-security-standards.
skills/implementing-pod-security-admission-controller/SKILL.md
Source commit 54a798831d2266a3ca61ce68a7acb80b81160d57
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 35,882
- Repository last updated
- Aug 31, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- cybersecurity Repository topic
- incident-response Repository topic
- mitre-attack Repository topic
- penetration-testing Repository topic
- red-team Repository topic
- security Repository topic
- cloud-security Repository topic
- malware-analysis Repository topic
- kubernetes Declared skill tag
- pod-security-admission Declared skill tag
- psa Declared skill tag
- pod-security-standards Declared skill tag
- admission-controller Declared skill tag
- devops Derived category
- security Derived category
- testing Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSEasset · 11,255 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesSKILL.mdcore · 9,801 bytesassets/template.mddoc · 1,290 bytesreferences/api-reference.mddoc · 5,229 bytesreferences/standards.mddoc · 1,099 bytesreferences/workflows.mddoc · 1,066 bytesscripts/agent.pyruns · 11,706 bytesscripts/process.pyruns · 5,185 bytes
Read excerpt
# Implementing Pod Security Admission Controller
## Overview
Pod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.
## When to Use
- Wiring PSA up on a cluster for the first time
- Setting cluster-wide default enforcement via `AdmissionConfiguration`
- Exempting system namespaces, service accounts, or runtime classes from enforcement
- Debugging why a pod was rejected, or why enforcement is silently not firing
- Staging a safe rollout: `warn` and `audit` first, `enforce` once violations reach zero