feat: bump kube-webhook-certgen to 1.4.3 #2697
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
github-actions
bot
added
size/XS
mesosphere-ci
added
ok-to-test
|
✅ Created Kommander branch to test kommander-applications changes: https://github.com/mesosphere/kommander/tree/kapps/main/sandy/cve-fix-kube-webhook-certgen |
Pull Request Test Coverage Report for Build 11210849765Details
💛 - Coveralls |
SandhyaRavi2403
removed
the
do-not-merge/testing
mhrabovcin
reviewed
Oct 3, 2024
mhrabovcin
reviewed
Oct 3, 2024
github-actions
bot
added
size/S
SandhyaRavi2403
force-pushed
the
sandy/cve-fix-kube-webhook-certgen
branch
from
e683ee6
to
fc897d1
Compare
mhrabovcin
reviewed
Oct 3, 2024
mesosphere-ci
added
the
do-not-merge/testing
SandhyaRavi2403
removed
the
do-not-merge/testing
SandhyaRavi2403
force-pushed
the
sandy/cve-fix-kube-webhook-certgen
branch
from
1f5449d
to
409757e
Compare
mesosphere-ci
added
the
do-not-merge/testing
SandhyaRavi2403
removed
the
do-not-merge/testing
SandhyaRavi2403
force-pushed
the
sandy/cve-fix-kube-webhook-certgen
branch
from
409757e
to
7fdebb9
Compare
mesosphere-ci
added
the
do-not-merge/testing
mhrabovcin
approved these changes
Oct 7, 2024
SandhyaRavi2403
removed
the
do-not-merge/testing
ArvinderPal09
pushed a commit
that referenced
this pull request
Oct 8, 2024
* feat: bump kube-webhook-certgen to 1.4.3 * fix: address review comments * fix: address review comments * fix: address review comments
ArvinderPal09
added a commit
that referenced
this pull request
Oct 8, 2024
This reverts commit 9121d23.
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 problem does this PR solve?:
bump kube-webhook-certgen to 1.4.3 with cve fix
`sandhya.ravi@GT9X7CVF5F kommander-applications % trivy i registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.3
2024-10-03T00:20:37+05:30 INFO Vulnerability scanning is enabled
2024-10-03T00:20:37+05:30 INFO Secret scanning is enabled
2024-10-03T00:20:37+05:30 INFO If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2024-10-03T00:20:37+05:30 INFO Please see also https://aquasecurity.github.io/trivy/v0.53/docs/scanner/secret#recommendation for faster secret detection
2024-10-03T00:20:39+05:30 INFO Detected OS family="debian" version="12.6"
2024-10-03T00:20:39+05:30 INFO [debian] Detecting vulnerabilities... os_version="12" pkg_num=3
2024-10-03T00:20:39+05:30 INFO Number of language-specific files num=1
2024-10-03T00:20:39+05:30 INFO [gobinary] Detecting vulnerabilities...
2024-10-03T00:20:39+05:30 WARN Using severities from other vendors for some vulnerabilities. Read https://aquasecurity.github.io/trivy/v0.53/docs/scanner/vulnerability#severity-selection for details.
registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.3 (debian 12.6)
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)`
Which issue(s) does this PR fix?:
https://jira.nutanix.com/browse/NCN-102769
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist