Repository navigation
Conversation
ahauserv
force-pushed
the
fix/helm-roll-on-operator-configmap
branch
from
October 13, 2026 10:01
6aa63f1 to
3d36770
Compare
The operator reads the trivy-operator ConfigMap once, at startup (configManager.Read in pkg/operator/operator.go), so a change to any trivyOperator.* value, such as scanJobAutomountServiceAccountToken, takes effect only after the pod is restarted by something else. The Deployment's checksum annotation covers only trivy-operator-config. Add a second one for configmaps/operator.yaml. The plugin ConfigMap is re-read on every GetConfig call and needs none.
ahauserv
force-pushed
the
fix/helm-roll-on-operator-configmap
branch
from
November 16, 2026 12:14
3d36770 to
27ccaca
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 operator reads the
trivy-operatorConfigMap once, at startup (configManager.Readinpkg/operator/operator.go). The Deployment's checksum annotation only coverstrivy-operator-config, so changing anytrivyOperator.*value through the chart, e.g.scanJobAutomountServiceAccountToken, updates the ConfigMap but not the running operator until its pod restarts for some other reason.This adds a second checksum annotation for
configmaps/operator.yaml, so those changes roll the Deployment the same way #2760 does fortrivy-operator-config. The plugin ConfigMap is re-read on everyGetConfigcall and needs none.deploy/static/trivy-operator.yamlcarries the rendered annotation.Related issues
trivy-operator-configonly.Checklist