Chainguard Container for kyverno-policy-reporter-plugin-kyverno

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/kyverno-policy-reporter-plugin-kyverno:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's kyverno-policy-reporter-plugin-kyverno image is compatible with the upstream Kyverno Policy Reporter plugin. It provides enhanced policy reporting capabilities specifically designed for Kyverno policy management.

Prerequisites

• Kubernetes cluster
• Kyverno installed and running
• Policy Reporter installed

Getting Started

Installing with Helm

First, install Kyverno if not already installed:

helm repo add kyverno https://kyverno.github.io/kyverno/
helm repo update
kubectl create namespace kyverno
helm install kyverno kyverno/kyverno --namespace kyverno

Next, install Policy Reporter with the Kyverno plugin enabled:

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

helm install policy-reporter policy-reporter/policy-reporter \
  --namespace kyverno \
  --set plugin.kyverno.enabled=true \
  --set plugin.kyverno.image.registry=cgr.dev \
  --set plugin.kyverno.image.repository=ORGANIZATION/kyverno-policy-reporter-plugin-kyverno \
  --set plugin.kyverno.image.tag=latest

Verifying the Installation

Check that all components are running:

kubectl get pods -n kyverno

You should see pods for:

• Kyverno controllers (admission, background, cleanup, reports)
• Policy Reporter
• Policy Reporter Kyverno Plugin

Testing the Plugin

Create a simple Kyverno policy:

apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: require-app-label
spec:
  admission: true
  background: true
  rules:
  - match:
      any:
      - resources:
          kinds:
          - Pod
    name: check-app-label
    validate:
      message: All pods must have an 'app' label
      pattern:
        metadata:
          labels:
            app: ?*
  validationFailureAction: Audit

Apply the policy:

kubectl apply -f policy.yaml

Test the plugin API endpoint:

kubectl port-forward -n kyverno svc/policy-reporter-kyverno-plugin 8080:8080 &
curl -s http://localhost:8080/v1/policies | jq

You should see your policy listed in the response.

Configuration

The plugin supports various configuration options through the Policy Reporter Helm chart values. Key configuration options include:

• Image configuration: Set custom registry, repository, and tag
• Resource limits: Configure CPU and memory limits
• Service configuration: Customize service ports and types
• Security settings: Configure security contexts and policies

Documentation and Resources

• Policy Reporter Documentation
• Kyverno Documentation
• Policy Reporter Helm Chart

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.