Skip to content

Configuration

You can configure Trivy-Operator to control it's behavior and adapt it to your needs. Aspects of the operator machinery are configured using environment variables on the operator Pod, while aspects of the scanning behavior are controlled by ConfigMaps and Secrets.

Operator Configuration

NAME DEFAULT DESCRIPTION
OPERATOR_NAMESPACE N/A See Install modes
OPERATOR_TARGET_NAMESPACES N/A See Install modes
OPERATOR_EXCLUDE_NAMESPACES N/A A comma separated list of namespaces (or glob patterns) to be excluded from scanning in all namespaces Install mode.
OPERATOR_TARGET_WORKLOADS All workload resources A comma separated list of Kubernetes workloads to be included in the vulnerability and config-audit scans
OPERATOR_SERVICE_ACCOUNT trivy-operator The name of the service account assigned to the operator's pod
OPERATOR_LOG_DEV_MODE false The flag to use (or not use) development mode (more human-readable output, extra stack traces and logging information, etc).
OPERATOR_SCAN_JOB_TTL "" The set automatic cleanup time after the job is completed
OPERATOR_SCAN_JOB_TIMEOUT 5m The length of time to wait before giving up on a scan job
OPERATOR_CONCURRENT_SCAN_JOBS_LIMIT 10 The maximum number of scan jobs create by the operator
OPERATOR_CONCURRENT_NODE_COLLECTOR_LIMIT 1 The maximum number of node collector jobs create by the operator
OPERATOR_SCAN_JOB_RETRY_AFTER 30s The duration to wait before retrying a failed scan job
OPERATOR_BATCH_DELETE_LIMIT 10 The maximum number of config audit reports deleted by the operator when the plugin's config has changed.
OPERATOR_BATCH_DELETE_DELAY 10s The duration to wait before deleting another batch of config audit reports.
OPERATOR_METRICS_BIND_ADDRESS :8080 The TCP address to bind to for serving Prometheus metrics. It can be set to 0 to disable the metrics serving.
OPERATOR_HEALTH_PROBE_BIND_ADDRESS :9090 The TCP address to bind to for serving health probes, i.e. /healthz/ and /readyz/ endpoints.
OPERATOR_VULNERABILITY_SCANNER_ENABLED true The flag to enable vulnerability scanner
OPERATOR_CONFIG_AUDIT_SCANNER_ENABLED false The flag to enable configuration audit scanner
OPERATOR_RBAC_ASSESSMENT_SCANNER_ENABLED true The flag to enable rbac assessment scanner
OPERATOR_CONFIG_AUDIT_SCANNER_SCAN_ONLY_CURRENT_REVISIONS true The flag to enable config audit scanner to only scan the current revision of a deployment
OPERATOR_CONFIG_AUDIT_SCANNER_BUILTIN true The flag to enable built-in configuration audit scanner
OPERATOR_VULNERABILITY_SCANNER_SCAN_ONLY_CURRENT_REVISIONS true The flag to enable vulnerability scanner to only scan the current revision of a deployment
OPERATOR_INFRA_ASSESSMENT_SCANNER_ENABLED true The flag to enable cluster infra assessment scanner
OPERATOR_CLUSTER_COMPLIANCE_ENABLED true The flag to enable cluster compliance scanner
OPERATOR_ACCESS_GLOBAL_SECRETS_SERVICE_ACCOUNTS true The flag to enable access to global secrets/service accounts to allow vulnerability scan job to pull images from private registries
OPERATOR_SCANNER_REPORT_TTL "24h" The flag to set how long a report should exist. When a old report is deleted a new one will be created by the controller. It can be set to "" to disabled the TTL for vulnerability scanner.
OPERATOR_LEADER_ELECTION_ENABLED false The flag to enable operator replica leader election
OPERATOR_LEADER_ELECTION_ID trivy-operator-lock The name of the resource lock for leader election
OPERATOR_EXPOSED_SECRET_SCANNER_ENABLED true The flag to enable exposed secret scanner
OPERATOR_WEBHOOK_BROADCAST_URL "" The flag to enable operator reports to be sent to a webhook endpoint. "" means that this feature is disabled
OPERATOR_BUILT_IN_TRIVY_SERVER false The flag to enable the usage of built-in trivy server in cluster. It also overwrites the following trivy params with built-in values: trivy.mode = ClientServer and serverURL = http://[server Service Name].[trivy Operator Namespace]:4975
OPERATOR_WEBHOOK_BROADCAST_TIMEOUT 30s The flag to set operator webhook timeouts, if webhook broadcast is enabled
OPERATOR_WEBHOOK_BROADCAST_CUSTOM_HEADERS "" The flag is a comma separated list of custom HTTP headers sent to a webhook endpoint.
OPERATOR_SEND_DELETED_REPORTS false The flag to enable sending deleted reports if webhookBroadcastURL is enabled
OPERATOR_PRIVATE_REGISTRY_SCAN_SECRETS_NAMES {} The flag is map of namespace:secrets, secrets are comma seperated which can be used to authenticate in private registries in case if there no imagePullSecrets provided example :
OPERATOR_MERGE_RBAC_FINDING_WITH_CONFIG_AUDIT false The flag to enable merging rbac finding with config-audit report
OPERATOR_SBOM_GENERATION_ENABLED true The flag to enable sbom generation

The values of the OPERATOR_NAMESPACE and OPERATOR_TARGET_NAMESPACES determine the install mode, which in turn determines the multitenancy support of the operator.

MODE OPERATOR_NAMESPACE OPERATOR_TARGET_NAMESPACES DESCRIPTION
OwnNamespace operators operators The operator can be configured to watch events in the namespace it is deployed in.
SingleNamespace operators foo The operator can be configured to watch for events in a single namespace that the operator is not deployed in.
MultiNamespace operators foo,bar,baz The operator can be configured to watch for events in more than one namespace.
AllNamespaces operators (blank string) The operator can be configured to watch for events in all namespaces.

Configuration from custom ConfigMap and/or Secret

When deployed with the Helm Chart, the environment variables for the Operator and Trivy Configuration are applied from the trivy-operator-config and trivy-operator-trivy-config ConfigMaps. It is possible to provide a custom ConfigMap and/or Secret to override these values. This is especially useful or even required, when configuration cannot be set through the Helm values, for example when some of the data is retrieved from external sources like Vault or other secret management systems in Cloud Provider environments. To apply values from a custom ConfigMap and/or Secret, the according Helm values need to be set:

  • operator.valuesFromConfigMap: The name of the ConfigMap to apply the values from. Will override the values trivy-operator-config ConfigMap.
  • operator.valuesFromSecret: The name of the Secret to apply the values from. Will override values from the trivy-operator-config AND operator.valuesFromConfigMap (if defined) ConfigMap.
  • trivy.valuesFromConfigMap: The name of the ConfigMap to apply the values from. Will override the values trivy-operator-trivy-config ConfigMap.
  • trivy.valuesFromSecret: The name of the Secret to apply the values from. Will override values from the trivy-operator-trivy-config AND trivy.valuesFromConfigMap (if defined) ConfigMap.

Example - configure namespaces to scan

To change the target namespace from all namespaces to the default namespace edit the trivy-operator Deployment and change the value of the OPERATOR_TARGET_NAMESPACES environment variable from the blank string ("") to the default value.

Scanning configuration

CONFIGMAP KEY DEFAULT DESCRIPTION
vulnerabilityReports.scanner Trivy The name of the plugin that generates vulnerability reports. Either Trivy or Aqua.
vulnerabilityReports.scanJobsInSameNamespace "false" Whether to run vulnerability scan jobs in same namespace of workload. Set "true" to enable.
scanJob.affinity N/A JSON representation of the affinity to be applied to the scanner pods and node-collector. Example: '{"nodeAffinity":{"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"kubernetes.io/os","operator":"In","values":["linux"]}]},{"matchExpressions":[{"key":"virtual-kubelet.io/provider","operator":"DoesNotExist"}]}]}}}'
scanJob.tolerations N/A JSON representation of the tolerations to be applied to the scanner pods and node-collector so that they can run on nodes with matching taints. Example: '[{"key":"key1", "operator":"Equal", "value":"value1", "effect":"NoSchedule"}]'
nodeCollector.volumeMounts see helm/values.yaml node-collector pod volumeMounts definition for collecting config files information
nodeCollector.volumes see helm/values.yaml node-collector pod volumes definition for collecting config files information
scanJob.nodeSelector N/A JSON representation of the [nodeSelector] to be applied to the scanner pods so that they can run on nodes with matching labels. Example: '{"example.com/node-type":"worker", "cpu-type": "sandylake"}'
scanJob.automountServiceAccountToken "false" The flag to enable automount for service account token on scan job. Set "true" to enable.
scanJob.skipInitContainers "false" When this flag is set to true, the initContainers will be skipped for the scanner and node collector pod. Set "true" to enable.
report.additionalLabels "" additionalReportLabels comma-separated representation of the labels which the user wants the reports to be labeled with. Example: foo=bar,env=stage will labeled the reports with the labels foo: bar and env: stage
scanJob.annotations N/A One-line comma-separated representation of the annotations which the user wants the scanner pods to be annotated with. Example: foo=bar,env=stage will annotate the scanner pods with the annotations foo: bar and env: stage
scanJob.templateLabel N/A One-line comma-separated representation of the template labels which the user wants the scanner pods to be labeled with. Example: foo=bar,env=stage will labeled the scanner pods with the labels foo: bar and env: stage
scanJob.podTemplatePodSecurityContext N/A One-line JSON representation of the template securityContext which the user wants the scanner pods to be secured with. Example: {"RunAsUser": 1000, "RunAsGroup": 1000, "RunAsNonRoot": true}
scanJob.podTemplateContainerSecurityContext N/A One-line JSON representation of the template securityContext which the user wants the scanner containers (and their initContainers) to be amended with. Example: {"allowPrivilegeEscalation": false, "capabilities": { "drop": ["ALL"]},"privileged": false, "readOnlyRootFilesystem": true }
report.resourceLabels N/A One-line comma-separated representation of the scanned resource labels which the user wants to include in the Prometheus metrics report. Example: owner,app,tier
metrics.resourceLabelsPrefix k8s_label Prefix that will be prepended to the labels names indicated in report.ResourceLabels when including them in the Prometheus metrics
report.recordFailedChecksOnly "true" this flag is to record only failed checks on misconfiguration reports (config-audit and rbac assessment)
skipResourceByLabels N/A One-line comma-separated labels keys which trivy-operator will skip scanning on resources with matching labels. Example: test,transient
node.collector.imageRef ghcr.io/aquasecurity/node-collector:0.0.6 The imageRef use for node-collector job .
node.collector.imagePullSecret N/A imagePullSecret is the secret name to be used when pulling node-collector image from private registries .
nodeCollector.excludeNodes "" excludeNodes comma-separated node labels that the node-collector job should exclude from scanning (example kubernetes.io/arch=arm64,team=dev)

Example - patch ConfigMap

By default Trivy displays vulnerabilities with all severity levels (UNKNOWN, LOW, MEDIUM, HIGH, CRITICAL). To display only HIGH and CRITICAL vulnerabilities by patching the trivy.severity value in the trivy-operator-trivy-config ConfigMap:

kubectl patch cm trivy-operator-trivy-config -n trivy-system \
  --type merge \
  -p "$(cat <<EOF
{
  "data": {
    "trivy.severity": "HIGH,CRITICAL"
  }
}
EOF
)"

Example - patch Secret

To set the GitHub token used by Trivy scanner add the trivy.githubToken value to the trivy-operator-trivy-config Secret:

kubectl patch secret trivy-operator-trivy-config -n trivy-system \
  --type merge \
  -p "$(cat <<EOF
{
  "data": {
    "trivy.githubToken": "$(echo -n <your token> | base64)"
  }
}
EOF
)"

Example - delete a key

The following kubectl patch command deletes the trivy.httpProxy key:

kubectl patch cm trivy-operator-trivy-config -n trivy-system \
  --type json \
  -p '[{"op": "remove", "path": "/data/trivy.httpProxy"}]'