chore(ci): Remove Trivy Action#426
Conversation
Signed-off-by: Andrey Velichkevich <andrey.velichkevich@gmail.com>
google-oss-prow
bot
requested review from
Electronic-Waste,
kramaranya and
szaher
There was a problem hiding this comment.
Pull request overview
Removes the scheduled Trivy CVE scanning/remediation GitHub Actions workflow from this repository’s CI configuration.
Changes:
- Deletes the
Trivy Vulnerability Scanworkflow (.github/workflows/trivy-cve-scan.yaml), including SARIF upload and automated dependency-fix PR creation.
Comments suppressed due to low confidence (1)
.github/workflows/trivy-cve-scan.yaml:1
- The PR description/title suggest removing the Trivy action from CI entirely, but this change only deletes the scheduled Trivy workflow;
.github/workflows/validate-lockfile.yamlstill runsaquasecurity/trivy-action@0.35.0on PRs (lines 57–79), so please either update the PR description/title to match the actual scope or remove/adjust the remaining Trivy usage as well.
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: franciscojavierarceo, kramaranya 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 |
|
/retest |
|
/cherry-pick release-0.4 |
|
@andreyvelich: new pull request created: #429 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
As per our discussion with the security team, we suggested to remove Trivy action from our CI at the moment.
/assign @akshaychitneni @astefanutti @tenzen-y @kramaranya @Fiona-Waters @franciscojavierarceo @juliusvonkohout @thesuperzapper