Digest pinning support for Trivy image.#2370
Open
Vinnie161 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Vitaliy P <vpr@lido.fi>
Vinnie161
force-pushed
the
feature/digest-pinning-support-for-trivy
branch
from
539079b to
f2ce44f
Compare
Collaborator
|
Let's discuss more in this thread |
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
2 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.
Summary
This change adds optional digest support for the Harbor Trivy adapter image.
Currently the Trivy StatefulSet always renders the image as:
This makes it impossible to use digest-based image references such as:
The new
trivy.image.digestvalue is optional and backward compatible:trivy.image.digestis empty, the chart keeps rendering<repository>:<tag>trivy.image.digestis set, the chart renders<repository>@<digest>This allows users to pin the Trivy adapter image by immutable digest while preserving the existing tag-based behavior by default.