Reduce Trivy Operator permissions#1224
Merged
jakub-racek-swi merged 7 commits intomasterfrom Dec 10, 2025
Merged
Conversation
gantrior
previously approved these changes
Dec 9, 2025
Co-authored-by: Eduard Tichy <17002066+etichy@users.noreply.github.com>
etichy
approved these changes
Dec 10, 2025
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
3 participants
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.
This PR will limit the permissions given to Trivy operator to reflect the only feature we use, that is image vulnerability scanning.
I have disabled access to secrets stored outside the Trivy namespace. To enable scanning of images stored in private registries, the user is able to grant the access rights to Trivy through either: