trivy-operator

Trivy Operator keeps security report resources updated. The Trivy Operator Helm chart automates deployment and configuration of Trivy Operator in Kubernetes clusters using Minimus images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges

Note: Trivy Operator uses Custom Resource Definitions (CRDs) for VulnerabilityReports, ConfigAuditReports, and related security resources. These CRDs are installed automatically as part of the Helm chart deployment.

Try It Out

In this example we will deploy Trivy Operator on a Kubernetes cluster using the Minimus Trivy Operator Helm chart. Trivy Operator will automatically scan your workloads for vulnerabilities and configuration issues.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns trivy-operator

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-trivy-operator oci://helm.mini.dev/trivy-operator \
  --version 0.36.0 \
  -n trivy-operator \
  --wait

If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:

helm install my-trivy-operator oci://helm.mini.dev/trivy-operator \
  --version 0.36.0 \
  -f values.yaml \
  -n trivy-operator \
  --wait

Step 4: Verify Trivy Operator is Running

Confirm the chart deployed successfully and Trivy Operator started:

kubectl get pods -n trivy-operator

You should see output similar to:

NAME                                       READY   STATUS    RESTARTS   AGE
my-trivy-operator-xxxxxxxxx-xxxxx          1/1     Running   0          2m

Step 5: Test Vulnerability Scanning

Trivy Operator automatically scans workloads in your cluster. Create a test deployment to trigger a scan:

kubectl create deployment trivy-test-app --image=nginx:latest -n trivy-operator

Wait a few minutes for the scan to complete, then check for VulnerabilityReports:

kubectl get vulnerabilityreports -n trivy-operator

You should see output similar to:

NAME                                    REPOSITORY      TAG      SCANNER   AGE
replicaset-trivy-test-app-xxxxxxxxx-nginx   nginx       latest   Trivy     1m

Clean up the test deployment:

kubectl delete deployment trivy-test-app -n trivy-operator

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-trivy-operator -n trivy-operator
kubectl delete namespace trivy-operator

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.