k8s-policy

To audit Kubernetes policy violations, use an audit-first workflow to retrieve policy reports from Kyverno or Gatekeeper. This identifies failed resource configurations so you can review violations before switching to active enforcement.

Yes, it supports managing both Kyverno ClusterPolicies and Gatekeeper constraints. It detects which policy engines are installed, lists active policies, and retrieves constraint details to validate enforcement logic.

You can list Kyverno ClusterPolicies by detecting the policy engine and retrieving policy details and reports. This lists what is enforced and checks current resource configurations against defined security rules.

The best way to detect installed policy engines is through automated readiness checks. This detects whether Kyverno and Gatekeeper are installed in your cluster before attempting policy operations.

Yes, you can retrieve Gatekeeper constraint details and templates. This allows you to inspect specific constraint configurations to review the expected inputs and enforcement logic applied to resources.

Reviewing policy reports before security enforcement catches misconfigurations before they reach production. This audit-first process validates resource compliance and prevents blocking deployments with unexpected policy violations.