kyverno-pod-security-templates

Enforce Kyverno Pod Security Standards with YAML policies and compliance reports.

3|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill kyverno-pod-security-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kyverno-pod-security-templates
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/enforce/skills/kyverno-pod-security-templates
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill kyverno-pod-security-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Pod security policies were deprecated in Kubernetes, and organizations need a reliable way to enforce security boundaries on workloads. Kyverno Pod Security Templates provide policy-based enforcement to maintain consistent security posture across clusters.

Core Features & Use Cases

  • Enforce Pod Security Standards (Baseline, Restricted) using Kyverno policies.
  • Implement privilege restrictions and non-root execution across deployments.
  • Apply policies via standard YAML files (standards.yaml, privileges.yaml, profiles.yaml) and validate via Kyverno reports.

Quick Start

Apply the standards.yaml, privileges.yaml, and profiles.yaml policies to enforce Kyverno pod security in your cluster.

Frequently Asked Questions about kyverno-pod-security-templates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Kubernetes pod security standards after PodSecurityPolicy deprecation?

You can enforce Kubernetes pod security standards using Kyverno policies. This skill applies policy-based enforcement to maintain consistent security posture by restricting privileged containers and mandating non-root execution across clusters.

How do I restrict privileged containers and enforce non-root execution in Kubernetes?

To restrict privileged containers and enforce non-root execution in Kubernetes, you apply Kyverno policies like privileges.yaml. These policies validate deployments and runtime namespaces to prevent insecure workload configurations.

What is the best way to validate Kyverno policy compliance for pod security?

The best way to validate Kyverno policy compliance is through Kyverno reports. After applying standards.yaml, privileges.yaml, and profiles.yaml policies, the reports confirm whether workloads satisfy the restricted and baseline security boundaries.

Can I use Kyverno pod security policies across clusters of any size and scope?

Yes, Kyverno pod security policies apply across clusters of any size and scope. The policies enforce seccomp profiles and privilege restrictions within deployment pipelines and runtime namespaces regardless of your cluster scale.

Do I need specific YAML files to implement baseline and restricted pod security standards with Kyverno?

Yes, you need to apply specific YAML files to implement pod security standards with Kyverno. The skill utilizes standards.yaml, privileges.yaml, and profiles.yaml to establish baseline and restricted security boundaries for your workloads.