> ## Documentation Index
> Fetch the complete documentation index at: https://radarhq.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Kyverno policy visibility in Kubernetes

> Audit Kyverno in Radar: Policy detail views with Enforce/Audit badges and rule breakdowns, plus PolicyReport charts of pass/fail results across the cluster.

[Kyverno](https://kyverno.io/) is a Kubernetes-native policy engine for validation, mutation, generation, and image verification  -  no new language required, policies are written as Kubernetes resources.

### What Radar Shows

**Policy / ClusterPolicy Detail View:**

* Failure action badge (Enforce in red, Audit in yellow)
* Configuration: background scanning, webhook timeout, failure policy, schema validation
* Rule type summary (validate/mutate/generate/verifyImages counts)
* Individual rules with type badges and match/exclude indicators
* Auto-generated rules list

**PolicyReport / ClusterPolicyReport Detail View:**

* Visual result bar chart (pass/fail/warn/error/skip proportions)
* Scope and source information
* Individual results with status badges, severity levels, policy/rule names
* Expandable details: message, category, source, affected resources
* Problem detection (AlertBanner for failures or errors)

**Resource Browser:** Smart columns show status (colored by worst outcome), failure action, rule counts, and pass/fail/warn/error/skip breakdowns.

### Supported CRDs

| CRD                 | Group                     | Topology | Detail View | AI Summary |
| ------------------- | ------------------------- | -------- | ----------- | ---------- |
| Policy              | `kyverno.io/v1`           | -        | Yes         | -          |
| ClusterPolicy       | `kyverno.io/v1`           | -        | Yes         | -          |
| PolicyReport        | `wgpolicyk8s.io/v1alpha2` | -        | Yes         | Yes        |
| ClusterPolicyReport | `wgpolicyk8s.io/v1alpha2` | -        | Yes         | Yes        |

PolicyReport findings are policy posture, not live operational failure, so they are **not** part of the `/api/issues` stream. They surface per-resource: the PolicyReport detail view (above) and the `resourceContext` policy rollup on a resource fetched via `get_resource`. (The cluster audit  -  `/api/audit` + MCP `get_cluster_audit`  -  is radar's own static best-practice scanner and does **not** include PolicyReport results.)