Update Helm release policy-reporter to v3.9.1 (main)

This MR contains the following updates:

Package Update Change
policy-reporter (source) minor 3.8.1 -> 3.9.1

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

kyverno/policy-reporter (policy-reporter)

v3.9.1

Compare Source

  • fix: update custom board crds, add resource and clusterResource filter

v3.9.0

Compare Source

Policy Reporter v3.9.0

  • feat: set GOMEMLIMIT on application startup based on container or system memory
  • feat: new resources filter which expects a resource string like pods.v1 or deployments.apps/v1
  • chore(email): use standardized http client config for graphapi
  • feat: support filter for results from the resolved namespaces api
  • feat: add replicaset owner check

Policy Reporter UI v2.7.0

  • feat: set GOMEMLIMIT on application startup based on container or system memory
  • feat: compact mode for default dashboards and custom boards
  • feat: applying custom board filters in the backend changes the previous behavior, in which configured filters were used as default filters in the UI. The new behavior applies these filters on the backend and makes it impossible to remove.
  • chore(security): the policy reporter core api is no longer exposed via a proxy URI. All requests are now done via the UI backend which applies configured filters and/or authentication.
  • feat(openidConnect): auto-detect and apply PKCE from OIDC discovery
  • feat: new cluster config to force attempt http2

Policy Reporter Kyverno Plugin v0.7.0

  • feat: set GOMEMLIMIT on application startup based on container or system memory

Policy Reporter Trivy Plugin v0.5.0

  • feat: set GOMEMLIMIT on application startup based on container or system memory

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.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


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

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)

Merge request reports

Loading
Loading