Policy-reporter Helm Chart

Policy-reporter
Analyzed version: 2.8.0

By Kyverno

Policy Reporter watches for PolicyReport Resources. It creates Prometheus Metrics and can send rule validation events to different targets like Loki, Elasticsearch, Slack or Discord

Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.

Latest version: 15.5.3
View GitHub

How to Install the Policy-reporter Helm Chart

Add Chart Repository to Helm

helm repo add policy-reporter https://kyverno.github.io/policy-reporter

Install Chart

helm install my-policy-reporter policy-reporter/policy-reporter --version 2.8.0

Does the Policy-reporter Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 5 of the best practices recommended by the industry.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Ensure each container has a configured CPU limit

1 occurrences:

  • metadata.name: release-name-policy-reporter (kind: Deployment)

💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Prevent container security vulnerability (CVE-2021-25741)

2 occurrences:

  • metadata.name: release-name-policy-reporter (kind: Deployment)

💡 Forbidden property object `subPath` - malicious users can gain access to files & directories outside of the volume

Learn how to fix the issue here

❌ Ensure each container has a configured memory request

1 occurrences:

  • metadata.name: release-name-policy-reporter (kind: Deployment)

💡 Missing property object `requests.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU request

1 occurrences:

  • metadata.name: release-name-policy-reporter (kind: Deployment)

💡 Missing property object `requests.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured memory limit

1 occurrences:

  • metadata.name: release-name-policy-reporter (kind: Deployment)

💡 Missing property object `limits.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

This is some text inside of a div block.
This is some text inside of a div block.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started