fix: write updated config back to mounted file on configmap reload - #1233
Open
AruneshDwivedi wants to merge 1 commit into
Open
fix: write updated config back to mounted file on configmap reload#1233AruneshDwivedi wants to merge 1 commit into
AruneshDwivedi wants to merge 1 commit into
Conversation
Kubernetes configmap updates are mounted as files, but the controller only updates its in-memory config. The trivy scanner pod reads the config file directly from the mount, so it sees the stale version. Write the marshaled config back to the file after Update() so that sidecar containers reading the mount see the updated configuration. Signed-off-by: Arunesh Dwivedi <arunesh.devops@gmail.com>
AruneshDwivedi
requested review from
ashnamehrotra,
pmengelbert and
sozercan
as code owners
August 20, 2026 06:38
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
1 participant
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.
Fixes #927
When Kubernetes updates a ConfigMap, the controller detects the change via inotify and updates its in-memory configuration. However, the trivy scanner pod reads the config file directly from the mounted volume, so it continues to see the stale version.
The bug:
The fix:
After updating the in-memory config, write the marshaled config back to the mounted file. This ensures sidecar containers reading the config file see the updated values.