Bump google.golang.org/grpc from 1.56.2 to 1.57.0

[dependabot]

Bumps google.golang.org/grpc from 1.56.2 to 1.57.0.

Release notes

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

Release 1.57.0

API Changes

• resolver: remove deprecated Target.Scheme and Target.Authority. Use URL.Scheme and URL.Host instead, respectively (#6363)

Behavior Changes

• client: percent-encode the default authority for the channel (#6428)
• xds: require EDS service name to be set in a CDS cluster with an 'xdstp' resource name (gRFC A47) (#6438)

New Features

• reflection: support the v1 reflection service and update Register to register both v1alpha and v1 (#6329)
• xds: add support for string matcher in RBAC header matching (#6419)
• alts: add support for GRPC_ALTS_MAX_CONCURRENT_HANDSHAKES env var (#6267)
• balancer/weightedroundrobin: de-experimentalize name of LB policy (#6477)

Bug Fixes

• status: status.FromError now returns an error with codes.Unknown when the error implements the GRPCStatus() method, and calling GRPCStatus() returns nil (#6374)
  • Special Thanks: @​atollena
• server: fix bug preventing TCP user timeout from being set on the connection when TLS is used (#6321)
  • Special Thanks: @​tobotg
• client: eliminate connection churn during an address update that differs only in balancer attributes (#6439)
• clusterresolver: handle EDS nacks, resource-not-found errors, and DNS Resolver errors correctly (#6436, #6461)
• xds/ringhash: cache connectivity state of subchannels inside picker to avoid rare races (#6351)

Commits

• 87bf02a Change version to 1.57.0 (#6448)
• 6b64be9 resolver/weighted_round_robin: remove experimental suffix from name
• 9489082 github: replace deprecated command with environment file (#6417)
• d1868a5 clusterresolver: add logs for dns discovery mechanism error cases (#6444)
• 8e9c8f8 grpc: do not use balancer attributes during address comparison (#6439)
• db32c5b Fix preloader mode in benchmarks (#6359)
• f0280f9 xds: require EDS service name in new-style CDS clusters (gRFC A47) (#6438)
• bf5b7ae clusterresolver: handle EDS nacks and resource-not-found errors correctly (#6...
• fc0aa46 client: encode the authority by default (#6428)
• 11feb0a resolver: delete Target.Scheme and Target.Authority (#6363)
• 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 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)

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	848676a
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/64d0e96ddf4c54000841dfa0

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

Hi @dependabot[bot]. 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/test-infra repository.

[rikatz]

/ok-to-test

[rikatz]

/lgtm
/approve

[strongjz]

/lgtm
/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

@strongjz: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you.

In response to this:

/lgtm
/cherry-pick release-1.8

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.

[rikatz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [rikatz,strongjz]

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

[k8s-infra-cherrypick-robot]

@strongjz: #10258 failed to apply on top of branch "release-1.8":

Applying: Bump google.golang.org/grpc from 1.56.2 to 1.57.0
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump google.golang.org/grpc from 1.56.2 to 1.57.0
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/lgtm
/cherry-pick release-1.8

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.