build: Tidy go files

[nirs]

It seems that recent dependencies changes were missing go mod tidy. Running it modified go.* files.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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 @nirs. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[medyagh]

its weird if I run go mod tidy in both folders it wont genearte a diff but if I do
go work sync it will do tht but the diff is in the hack/go.mod do u mind trying go work sync?

lets make this PR ina way that runs go work sync automatically

[nirs]

I run go work sync, it updated hack/go.mod. Posted at a new commit.

I'm not sure what go work sync is doing, and when you don't want to run it.

I think we should run this in the CI to ensure that all PRs are tidy. This will tell the author when go mod tidy or do work sync should run.

[k8s-ci-robot]

PR needs rebase.

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.