Update dependency go modules for k8s v1.28.0-rc.0

[Sneha-at]

Ran kubernetes-csi/release-tools go-get-kubernetes.sh -p 1.28.0-rc.0

NONE

[k8s-ci-robot]

Welcome @Sneha-at!

It looks like this is your first PR to kubernetes-csi/node-driver-registrar 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/node-driver-registrar has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Sneha-at. Thanks for your PR.

I'm waiting for a kubernetes-csi 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/test-infra repository.

[jsafrane]

/ok-to-test

[mauriciopoppe]

I think you synced release-tools at the same time as bumping a library, could you please split the PRs?

[sunnylovestiramisu]

@mauriciopoppe syncing release-tools and bumping dependencies in the PR is intended according to the script we have. But we can probably separate them into two commits in the same PR.

[mauriciopoppe]

I understand and it's already in 2 commits so it's good

/lgtm
/approve

[mauriciopoppe]

/assign @msau42 @jsafrane
For approval

[msau42]

There's a few more changes in release tools we should pick up. Can you refresh the release-tools update after kubernetes-csi/csi-release-tools#229 merges?

[sunnylovestiramisu]

@msau42 we still need to do the v1.28.0 release as well later, release-tool update will be picked up after this PR?

[msau42]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mauriciopoppe, msau42, Sneha-at

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [msau42]

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