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

[dependabot]

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

Release notes

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

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

• server: for unary requests, free raw request message data as soon as parsing is finished instead of waiting until the method handler returns. (#7998)
  • Special Thanks: @​lqs

Documentation

• examples/features/gracefulstop: add example to demonstrate server graceful stop. (#7865)

Release 1.69.4

Bug Fixes

• rbac: fix support for :path header matchers, which would previously never successfully match (#7965).

Documentation

• examples/features/csm_observability: update example client and server to use the helloworld service instead of echo service (#7945).

Release 1.69.3 was accidentally tagged on the master branch and will be deleted. Please update to 1.69.4 instead.

Release 1.69.2

Bug Fixes

• stats/experimental: add type aliases for symbols (Metrics/etc) that were moved to the stats package (#7929).
• client: set user-agent string to the correct version.

Release 1.69.0

Known Issues

• The recently added grpc.NewClient function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. A fix is expected to be a part of grpc-go v1.70. (#7556)

New Features

• stats/opentelemetry: Introduce new APIs to enable OpenTelemetry instrumentation for metrics on servers and clients (#7874)
• xdsclient: add support to fallback to lower priority servers when higher priority ones are down (#7701)
• dns: Add support for link local IPv6 addresses (#7889)
• The new experimental pickfirst LB policy (disabled by default) supports Happy Eyeballs, interleaving IPv4 and IPv6 address as described in RFC-8305 section 4, to attempt connections to multiple backends concurrently. The experimental pickfirst policy can be enabled by setting the environment variable GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST to true. (#7725, #7742)

... (truncated)

Commits

• 98a0092 Change version to 1.70.0 (#7984)
• bf380de Cherrypick #7998, #8011, #8010 into 1.70.x (#8028)
• 54b3eb9 experimental/credentials: Add credentials that don't enforce ALPN (#7980) (#8...
• 62b9185 clustetresolver: Copy endpoints.Addresses slice from DNS updates to avoid dat...
• 724f450 examples/features/csm_observability: use helloworld client and server instead...
• e8d5feb rbac: add method name to :path in headers (#7965)
• e912015 cleanup: Fix usages of non-constant format strings (#7959)
• 681334a cleanup: replace dial with newclient (#7943)
• 063d352 internal/resolver: introduce a new resolver to handle target URI and proxy ad...
• 10c7e13 outlierdetection: Support health listener for ejection updates (#7908)
• 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-1473) was allocated in production infra for this PR.

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

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1473 --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 install-local

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

[dependabot]

Superseded by #1505.