Repository navigation
test: add fallback registries for Trivy vulnerability database - #642
Merged
andyzhangx merged 1 commit intoOct 24, 2026
Merged
Conversation
Signed-off-by: andyzhangx <xiazhang@microsoft.com>
kubernetes-prow
Bot
added
kind/bug
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
approved
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Apply the same Trivy database repository fallback as kubernetes-csi/csi-driver-smb#1245.
The workflow currently configures ECR Public as its only vulnerability database source. If ECR returns
TOOMANYREQUESTS: Data limit exceeded, Trivy cannot initialize its database and the scan fails before inspecting the image.Configure the following ordered fallback list for every Trivy scan step in this workflow:
mirror.gcr.io/aquasec/trivy-db:2ghcr.io/aquasecurity/trivy-db:2public.ecr.aws/aquasecurity/trivy-db:2Trivy can try another repository on transient errors such as HTTP 429 and 5xx. Preserve all existing image references, build steps, action pins, scan severities, and
exit-code: '1'. This does not ignore vulnerability findings or bypass scanner failures.Reference: https://trivy.dev/docs/latest/configuration/db/#database-locations
Which issue(s) this PR fixes:
Related to kubernetes-csi/csi-driver-smb#1245; prevents the same single-registry database-download failure in this repository.
Special notes for your reviewer:
Local validation:
git diff --checkpassed.TRIVY_DB_REPOSITORYlists in the Trivy steps.exit-code: '1'.Full image builds and Trivy scans were not run locally; CI will exercise them. Multiple repositories reduce single-registry dependency but do not guarantee availability if every source fails.
Does this PR introduce a user-facing change?: