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

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-trivy: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-trivy image is compatible with the upstream Trivy Policy Reporter plugin. It provides vulnerability scanning and security reporting capabilities integrated with Policy Reporter.

Prerequisites

• Kubernetes cluster
• Kyverno installed and running
• Trivy Operator for vulnerability scanning
• Policy Reporter with UI enabled

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 the Trivy Operator for vulnerability scanning:

helm repo add aqua https://aquasecurity.github.io/helm-charts
helm repo update
helm install trivy-operator aqua/trivy-operator \
  --namespace trivy-system \
  --create-namespace

Then, install Policy Reporter with the Trivy 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 ui.enabled=true \
  --set plugin.trivy.enabled=true \
  --set plugin.trivy.image.registry=cgr.dev \
  --set plugin.trivy.image.repository=ORGANIZATION/kyverno-policy-reporter-plugin-trivy \
  --set plugin.trivy.image.tag=latest

Verifying the Installation

Check that all components are running:

kubectl get pods -n kyverno
kubectl get pods -n trivy-system

You should see pods for:

• Kyverno namespace: Kyverno controllers (admission, background, cleanup, reports), Policy Reporter, Policy Reporter Trivy Plugin
• Trivy-system namespace: Trivy Operator

Testing the Plugin

The Trivy plugin processes vulnerability data from the Trivy Operator and sends it to Policy Reporter. To test the complete workflow:

# Create a test pod for Trivy Operator to scan
kubectl run nginx-test --image=nginx:1.24 --namespace=default

# Wait for the pod to be ready and Trivy to scan it
kubectl wait --for=condition=ready pod nginx-test --namespace=default --timeout=60s

# Give Trivy Operator time to scan and create vulnerability reports
sleep 30

# Port-forward to the Policy Reporter UI
kubectl port-forward -n kyverno svc/policy-reporter-ui 8080:8080 &

# Check for Trivy vulnerability results
curl -s "http://127.0.0.1:8080/proxy/default/core/v1/namespaced-resources/results?sources=trivy&categories=Vulnerability+Scan&namespaces=default&page=1&offset=10"

You should see vulnerability reports for the nginx:1.24 image. The plugin automatically:

1. Monitors VulnerabilityReports created by Trivy Operator
2. Processes vulnerability data from scanned container images
3. Forwards enriched vulnerability information to Policy Reporter
4. Provides data through Policy Reporter's API and UI

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
• Trivy Documentation
• Trivy Operator Documentation
• Policy Reporter Helm Chart
• Trivy Operator Helm Chart

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.