chore(deps): bump google.golang.org/grpc from 1.60.1 to 1.61.1

[dependabot]

Bumps google.golang.org/grpc from 1.60.1 to 1.61.1.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.61.1

Bug Fixes

• server: wait to close connection until incoming socket is drained (with timeout) to prevent data loss on client-side (#6977)
  • Special Thanks: @​s-matyukevich for discovering the root cause

Release 1.61.0

New Features

• resolver: provide method, AuthorityOverrider, to allow resolver.Builders to override the default authority for a ClientConn. (EXPERIMENTAL) (#6752)
  • Special Thanks: @​Aditya-Sood
• xds: add support for mTLS Credentials in xDS bootstrap (gRFC A65) (#6757)
  • Special Thanks: @​atollena
• server: add grpc.WaitForHandlers ServerOption to cause Server.Stop to block until method handlers return. (EXPERIMENTAL) (#6922)

Performance Improvements

• grpc: skip compression of empty messages as an optimization (#6842)
  • Special Thanks: @​jroper
• orca: use atomic pointer to improve performance in server metrics recorder (#6799)
  • Special Thanks: @​danielzhaotongliu

Bug Fixes

• client: correctly enable TCP keepalives with OS defaults on windows (#6863)
  • Special Thanks: @​mmatczuk
• server: change some stream operations to return UNAVAILABLE instead of UNKNOWN when underlying connection is broken (#6891)
  • Special Thanks: @​mustafasen81
• server: fix GracefulStop to block until all method handlers return (v1.60 regression). (#6922)
• server: fix two bugs that could lead to panics at shutdown when using NumStreamWorkers (EXPERIMENTAL). (#6856)
• reflection: do not send invalid descriptors to clients for files that cannot be fully resolved (#6771)
  • Special Thanks: @​jhump
• xds: don't fail channel/server startup when xds creds is specified, but bootstrap is missing certificate providers (#6848)
• xds: Atomically read and write xDS security configuration client side (#6796)
• xds/server: fix RDS handling for non-inline route configs (#6915)

Commits

• c6e7f04 Change version to 1.61.1 (#6981)
• dbd4cbc cherry-pick #6977 to 1.61.x release branch (#6980)
• 57ed608 Change version to 1.61.1-dev (#6937)
• 8167bc3 Change version to 1.61.0 (#6936)
• 52e2363 test/xds: Use different import path for gRPC Messages (#6933)
• 67e50be transport: Remove redundant if in handleGoAway (#6930)
• e96f521 alts: Extract AuthInfo after handshake in ALTS e2e test. (#6931)
• 987df13 metadata: move FromOutgoingContextRaw() to internal (#6765)
• 61eab37 server: block GracefulStop on method handlers and make blocking optional for ...
• ddd377f xds/server: fix RDS handling for non-inline route configs (#6915)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[k8s-ci-robot]

Hi @dependabot[bot]. 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.

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.

[andyzhangx]

/retest

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, dependabot[bot]

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 [andyzhangx]

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]

@dependabot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-azuredisk-csi-driver-e2e-capz-windows-2019-hostprocess	064813a	link	unknown	/test pull-azuredisk-csi-driver-e2e-capz-windows-2019-hostprocess
pull-azuredisk-csi-driver-e2e-capz-windows-2022	064813a	link	unknown	/test pull-azuredisk-csi-driver-e2e-capz-windows-2022

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.