kyverno-reports-server

Chainguard Container for kyverno-reports-server

Reports server provides a scalable solution for storing policy reports and cluster policy reports. It moves reports out of etcd and stores them in a PostgreSQL database instance.

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-reports-server:latest

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

Compatibility Notes

This image is based on the upstream reports-server image, with the following differences:

• Like all other Chainguard Containers, kyverno-reports-server features a stripped down, minimal design container image
• It has few-to-zero CVEs

The kyverno/reports-server Helm chart v0.1.5 uses an outdated PostgreSQL image reference due to an upstream change. The issue has been resolved in main and it should fixed in later versions.

Getting Started

Deploying Reports Server with Chainguard's images is straightforward using the official Kyverno Helm charts.

First, add the Kyverno reports-server Helm repository:

helm repo add reports-server https://kyverno.github.io/reports-server
helm repo update

Deploy the reports-server chart.

helm upgrade --install reports-server reports-server/reports-server \
    --set image.registry=cgr.dev \
    --set image.repository=chainguard/kyverno-reports-server \
    --set image.tag=latest

In order to use reports-server, you need a policy engine. We will use Kyverno for the purposes of this demo. Deploy kyverno using helm:

helm repo add kyverno https://kyverno.github.io/kyverno/
helm repo update

helm upgrade --install kyverno kyverno/kyverno \
    --namespace kyverno \
    --create-namespace \
    --set crds.reportsServer.enabled=true

For detailed instructions on deploying Reports Server via Helm, consult the official Reports Server Helm chart documentation.

Usage With Reports Server & Kyverno running, you can now create policies (or cluster policies) and check if they are migrated to the postgres database:

cat > "policy.yaml" <<'EOF'
apiVersion: kyverno.io/v1
kind: Policy
metadata:
  name: ns-require-app-label
  namespace: default
spec:
  validationFailureAction: Audit
  rules:
    - name: require-app-label
      match:
        any:
          - resources:
              kinds:
                - Pod
      validate:
        message: "app label is required (ns policy)"
        pattern:
          metadata:
            labels:
              app: "?*"
EOF

cat > "good-pod.yaml" <<'EOF'
apiVersion: v1
kind: Pod
metadata:
  name: good-pod
  namespace: default
  labels:
    app: web
spec:
  containers:
    - name: nginx
      image: nginx:1.25
EOF

kubectl apply -f policy.yaml
kubectl apply -f good-pod.yaml

# Now wait until the policy reports show up in kubernetes, then check if they exist in postgres
kubectl get policyreports

# The default postgres password set by the helm chart is "reports"
kubectl exec reports-server-postgresql-0 -- \
    sh -c "PGPASSWORD=reports psql -U postgres -d reportsdb -c 'SELECT * FROM policyreports;'"

# You should now see your policy reports here

Documentation and Resources

For more information about Reports-Server in container images, please refer to the kyverno website or to the official repository.

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.