SKIP UPGRADE Update kyverno-reporter to v3.7.0

The Upgrade is skipped in this MR since the cypress test fails due to duplicate "PolicyReports" dashboard in Grafana. The attached screenshots from running upgrade locally, show that upgrade does work as expected -- just the BB helm test breaks in pipeline with the duplicate dashboard.

The Upgrade Notice section below explains how to resolve this issue post install.

This MR contains the following updates:

Package	Update	Change
gluon	patch	0.9.2 -> 0.9.6
registry1.dso.mil/ironbank/nirmata/policy-reporter/policy-reporter-ui (source)	minor	2.4.4 -> 2.5.0
registry1.dso.mil/ironbank/opensource/kubernetes/kubectl (source)	minor	v1.33.5 -> v1.34.2
registry1.dso.mil/ironbank/opensource/kyverno/policy-reporter (source)	minor	3.5.0 -> 3.6.0
registry1.dso.mil/ironbank/opensource/kyverno/policy-reporter/kyverno-plugin (source)	patch	0.5.1 -> 0.5.2

Complete MR checklist

Assignee

• Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
• Update Docs with new/updated steps as needed
• Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

See comments

Linked Issue

Issue #136 (closed)

Reviewer only

• Tested and Validated changes

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this MR, check this box

---

This MR was automatically generated by Renovate Bot.

Upgrade Notices

The upgrade of policy-reporter from version 3.5.0 to version 3.7.0 results in a duplicate "PolicyReports" dashboard in the grafana monitoring tool. This is related to the introduction of a new, dashboard uid property which was added to the upstream monitoring package in v3.7.0 .

To remove the prior, duplicate dashboard, you can run the following command any time post-upgrade: kubectl -n monitoring rollout restart deployment monitoring-grafana . This will bounce the grafana server.