feat: add options to Helm chart to load Trivy config from custom configmap or secret #2174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The helm chart already provides
operator.valuesFromConfigMap
andoperator.valuesFromSecret
keys to set environment variables for the operator from a configmap or secret.This PR adds this feature also for the trivy configuration, e.g. to set a Proxy from external secret.
trivy.valuesFromConfigMap
will overwrite values in the following order:trivy-operator-trivy-config
default ConfigMaptrivy-operator-trivy-config
Secret generated by the Helm Charttrivy.valuesFromSecret
will overwrite values in the following order:trivy-operator-trivy-config
default ConfigMaptrivy-operator-trivy-config
Secret generated by the Helm Charttrivy.valuesFromConfigMap
ConfigMap (if specified)Related issues
Checklist