# Kyverno v1.15.2

2025-09-18 · [Original release notes](https://github.com/kyverno/kyverno/releases/tag/v1.15.2) · [Full summary](https://ratatosk.io/en/releases/kyverno/v1.15.2)

Breaking changes 4 · Important fixes 6 · Other changes 7

## Breaking changes (4)

### Namespace-termination report errors logged at DEBUG

- Affects: report creation in validation enforcement and audit paths

Previously, expected report-creation failures during namespace termination were logged at ERROR. Genuine access-denied and other forbidden errors remain at ERROR.

Evidence: “This PR fixes noisy ERROR logs in Kyverno when reports fail during namespace termination. Such expected errors are now logged at DEBUG instead of ERROR, reducing unnecessary alerts. Genuine access issues remain logged at ERROR, ensuring real security problems are still visible.” https://github.com/kyverno/kyverno/pull/13866

> * Fixed namespace termination logging (#13866)

### Resource filtering added to background scans for VAPs, MAPs, and new Kyverno policy types

- Affects: background scans for VAPs, MAPs, or new Kyverno policy types with `skipRespourceFilter` set to false and a configured `resourceFilter`

During these scans, resources matching the configured `resourceFilter` are skipped.

Evidence: “Applies resourceFilter on VAPs / MAPs and the new Kyverno policy types during background scan when skipRespourceFilter is set to false.” https://github.com/kyverno/kyverno/pull/13919

> * Fixed background scan reporting to consume `resourceFilter` for new policy types (#13919)

### `PolicyException` namespace matching uses resource namespace labels

- Affects: cluster processing of `PolicyException` resources with namespace selectors (Inferred)

If the resource namespace lookup fails, no exception is matched.

Evidence: “This PR retrieves the resource's namespace labels in order to check if the exception's namespace selector matches it.” https://github.com/kyverno/kyverno/pull/13975

> * Fixed namespace selector matching for PolicyException (#13975)

### OpenReports CRD installation gets a separate setting

- Affects: Helm chart configurations using OpenReports (Inferred)
- Action required: For CRD installation, `openreports.enabled` must also be true when `openreports.installCrds` is true.

Previously, `openreports.enabled: true` also installed the OpenReports CRDs. Now installation is controlled by `openreports.installCrds`, which defaults to `false`, so configurations without that value no longer install them.

Evidence: “| openreports.installCrds | bool | `false` | Whether to install CRDs from the upstream OpenReports chart. Setting this to true requires enabled to also be true.” https://github.com/kyverno/kyverno/pull/13924

> * Split openreports CRD installation from controller flag enabling in the helm chart (#13924)

## Important fixes (6)

### Admission matching for API-generated resource names fixed

- Affects: VAP or MAP admission matching with configured `resourceNames` (Inferred)

When an admission resource has an empty name because the API server will generate it, the matcher now matches it if its `generateName` starts with a configured `resourceNames` entry; without a matching prefix, it skips that name match.

> * Fixed resource name matching for edge case when name is auto-generated (#13584)

### CLI user information now passed to VAP and MAP evaluation

- Affects: CLI evaluations of VAPs or MAPs with user information supplied (Inferred)

> * Fixed issue to evaluate userInfo for VAPs and MAPs in the CLI (#13920)

### Kyverno CLI `apply` maps skipped generate rules to skip

- Affects: Resources evaluated by generate rules through `kyverno apply` (Inferred)

Previously, the shown skipped response was counted as `fail: 1` and made the command exit with code 1; it now exits with code 0.

> * Fixed CLI apply command return code regardless of output format (#12629)

### Helm chart validation uses the reports-server CRD setting

- Affects: reports-server CRD settings in the Kyverno Helm chart (Inferred)

When `.Values.reportsServer.enabled` was absent, `helm template` failed with a nil-pointer error. The validation checks now read `.Values.crds.reportsServer.enabled`.

> * Updated conditional logic to correct `reportsServer` value reference (#13893)

### Mutating policy compilation errors blocked at admission

- Affects: mutating policies using JSON patch or apply-configuration expressions (Inferred)

When a mutating policy has a compilation error, its admission response includes a warning.

> * Fixed issue to block mutating policies upon compilation errors (#13972)

### Corrected `webhooksCleanup` image repository handling

- Affects: Helm chart configurations customizing `webhooksCleanup.image.repository` or `webhooksCleanup.image.registry` (Inferred)

When `webhooksCleanup.image.repository` was set to `myCustomRepo`, the cleanup image path became `myCustomRepo/registry.k8s.io/kubectl`.

> * Fixed repository customization for helm hooks (#13933)

## Other changes (7)

- Helm pre-delete hook Job suffixes shortened
- Helm chart VAP requirement warnings removed
- `validate.assert` now uses a pointer to `AssertionTree`
- Unit test added for `pkg/background/dynamic_watcher.go`
- Tests added for VAPs matching subresources
- Chainsaw tests fixed
- Background controller namespace lookup uses a namespace lister

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
