automation setup for the dependency vulnerability robot

[Oneimu]

Changes include:

1. Adds an automated workflow to run the vulnerability robot (daily and on-demand) so the repo gets proactive vulnerability scans and creates PRs to propose fixes—reducing manual effort and speeding remediation.
2. Fix depencies vulnerability related to google.golang.org/grpc

How to use it:

• Fully Automated: You don't need to do anything. Every morning, if a new vulnerability fix is available for your dependencies, you will find a new PR waiting in
  your repository.
• Manual Check: You can run it locally with python3 vuln_robot.py to see vulnerabilities without creating a PR, or with --create-pr to trigger the full robot flow.

[netlify]

✅ Deploy Preview for agent-sandbox canceled.

Name	Link
🔨 Latest commit	b714acd
🔍 Latest deploy log	https://app.netlify.com/projects/agent-sandbox/deploys/69cafb1bf36b6c0008b0e487

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Oneimu
Once this PR has been reviewed and has the lgtm label, please assign janetkuo for approval. For more information see the 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

[k8s-ci-robot]

Hi @Oneimu. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[justinsb]

Thanks @Oneimu . I think one challenge here is that we generally (in the kubernetes projects) don't like PRs to be sent from github actions. So I think it's great to add the script (though maybe name it dev/tools/vuln-robot), but I don't think we want to plug it into github.

We could also turn on dependabot for automation. Personally I think having your script + dependabot should give us good coverage - WDYT?

/assign

[k8s-ci-robot]

PR needs rebase.

Details

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-sigs/prow repository.