chore(ci): Remove Trivy Action - Trainer

[sameerdattav]

Removing trivy action - as instructed by @andreyvelich following kubeflow/katib#2644

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign astefanutti for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🎉 Welcome to the Kubeflow Trainer! 🎉

Thanks for opening your first PR! We're happy to have you as part of our community 🚀

Here's what happens next:

• If you haven't already, please check out our Contributing Guide for repo-specific guidelines and the Kubeflow Contributor Guide for general community standards.
• Our team will review your PR soon! cc @kubeflow/kubeflow-trainer-team

Join the community:

• Slack: Join our #kubeflow-trainer Slack channel.
• Meetings: Attend the Kubeflow AutoML and Training Working Group bi-weekly meetings.

Feel free to ask questions in the comments if you need any help or clarification!
Thanks again for contributing to Kubeflow! 🙏

[Copilot]

Pull request overview

Removes the Trivy vulnerability scanning GitHub Action workflow from the repository, aligning this repo with the referenced upstream guidance.

Changes:

• Deleted .github/workflows/trivy-scan.yaml to stop running Trivy scans and uploading SARIF results.

Comments suppressed due to low confidence (1)

.github/workflows/trivy-scan.yaml:1

• Removing the Trivy workflow leaves this repo with no vulnerability/code scanning GitHub Actions workflow (no other trivy/codeql/SARIF upload found under .github/workflows), so please confirm there is an alternative org-level/centralized scanning solution in place or replace this with the new recommended security scanning approach referenced in kubeflow/katib#2644.

[google-oss-prow]

@Sridhar1030: changing LGTM is restricted to collaborators

Details

In 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.

[andreyvelich]

/close
Removed here: #3389

[google-oss-prow]

@andreyvelich: Closed this PR.

Details

In response to this:

/close
Removed here: #3389

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.