chore(deps): bump google.golang.org/grpc from 1.62.1 to 1.71.0

[dependabot]

Bumps google.golang.org/grpc from 1.62.1 to 1.71.0.

Release notes

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

Release 1.71.0

API Changes

• balancer: Custom LB policies that record metrics must use the new MetricsRecorder method on Balancer.ClientConn instead of the removed Balancer.BuildOptions.MetricsRecorder field to obtain a metrics recorder. (#8027)
• balancer: balancer.ClientConn implementations must now embed a delegate implementation. This allows grpc-go to add new methods to the interface and remain backward compatible. (#8026)
• balancer/endpointsharding: The constructor accepts the child balancer's builder and a struct with optional configuration. (#8052)

New Features

• xds: Add support for dualstack via the additional_addresses field in the Endpoint resource. To disable this feature, set the environment variable GRPC_EXPERIMENTAL_XDS_DUALSTACK_ENDPOINTS=false. (#8134)
• stats/opentelemetry: Add experimental support for OpenTelemetry tracing. (#7852)
• xds/internal/xdsclient: Add counter metrics for valid and invalid resource updates. (#8038)
• balancer/leastrequest, roundrobin: Add dualstack support. (#7969, #7966)
• balancer/endpointsharding: Balancers created with the new DisableAutoReconnect option will not attempt to call ExitIdle automatically on their children when the children report idle. (#8052)

Bug Fixes

• client: Fix support for proxies when using grpc.NewClient so the target is resolved by the proxy as expected. (#7881)
  • Added WithLocalDNSResolution() dial option to explicitly force target resolution on the client instead. (#7881)
• weightedtarget: Return erroring picker when no targets are configured. (#8070)
• xds: Fail RPCs with UNAVAILABLE when the EDS resource is missing or contains no endpoints (#8070)
• xdsclient: Fix a bug where connectivity failures were reported to resource watchers before trying all listed servers. (#8075)
• grpc: Fix the number of bytes reported in the error message when encoded messages are larger than 4GB. (#8033)
• xds: Fixed a bug preventing tests from creating multiple servers or channels with different bootstrap configs. (#8050)
• grpc: Fix message length checks when compression is enabled and maxReceiveMessageSize is MaxInt (#7918)
  • Special Thanks: @​vinothkumarr227

Documentation

• client: Improve documentation of grpc.NewClient and ClientConn.CanonicalTarget by providing examples. (#8078)
• examples/features/dualstack: New example demonstrating usage of endpoints and dualstack functionality. (#8098)

Release 1.70.0

Behavior Changes

• client: reject service configs containing an invalid retryPolicy in accordance with gRFCs A21 and A6. (#7905)
  • Note that this is a potential breaking change for some users using an invalid configuration, but continuing to allow this behavior would violate our cross-language compatibility requirements.

New Features

• xdsclient: fallback to a secondary management server (if specified in the bootstrap configuration) when the primary is down is enabled by default. Can be disabled by setting the environment variable GRPC_EXPERIMENTAL_XDS_FALLBACK to false. (#7949)
• experimental/credentials: experimental transport credentials are added which don't enforce ALPN. (#7980)
  • These credentials will be removed in an upcoming grpc-go release. Users must not rely on these credentials directly. Instead, they should either vendor a specific version of gRPC or copy the relevant credentials into their own codebase if absolutely necessary.

Bug Fixes

• xds: fix a possible deadlock that happens when both the client application and the xDS management server (responsible for configuring the client) are using the xds:/// scheme in their target URIs. (#8011)

Performance

... (truncated)

Commits

• d01db5c Change version to 1.71.0 (#8105)
• 012f8bf xds: Enable dualstack flag (#8134)
• bf0c885 examples/features/dualstack: Demonstrate Dual Stack functionality (#8098) (#8...
• 05bdd66 ringhash: Remove TODO comment (#8096)
• ddb2484 xds: remove obsolete xDS transport custom dialer option (#8079)
• 8528f43 cleanup: replace Dial with NewClient (#7975)
• ae2a04f ringhash: Replace DNS resolver before sending xDS Update in test (#8091)
• e55819e lazy: Use channel to wait for resolver error being received in test (#8088)
• b524c08 xdsclient: include xds node ID in errors from the WatchResource API (#8093)
• 91eb6aa client: improve documentation of target strings (#8078)
• 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)

[rhacs-bot]

A single node development cluster (infra-pr-1505) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server:0.10.95-1-g1c85757193 to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1505 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f