Vulnerability patch in secret-sync #3575
Merged
Conversation
This file contains 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
jupyterhub-bot
added
the
image:rebuild-to-patch-vuln
consideRatio
pushed a commit
to jupyterhub/helm-chart
that referenced
this pull request
Nov 19, 2024
jupyterhub/zero-to-jupyterhub-k8s#3575 Merge pull request #3575 from jupyterhub/vuln-scan-secret-sync
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.
A rebuild of
quay.io/jupyterhub/k8s-secret-synchas been found to influence the detected vulnerabilities! This PR will trigger a rebuild because it has updated a comment in the Dockerfile.About
This scan for known vulnerabilities has been made by aquasecurity/trivy. Trivy was configured to filter the vulnerabilities with the following settings:
trueBefore
Before trying to rebuild the image, the following vulnerabilities was detected in
quay.io/jupyterhub/k8s-secret-sync:4.0.1-0.dev.git.6864.hfc323db4.After