container-object-storage-interface-provisioner-sidecar
container-object-storage-interface-provisioner-sidecar copied to clipboard
Bump google.golang.org/grpc from 1.63.2 to 1.65.0
Bumps google.golang.org/grpc from 1.63.2 to 1.65.0.
Release notes
Sourced from google.golang.org/grpc's releases.
Release 1.65.0
Dependencies
- Change support policy to cover only the latest TWO releases of Go, matching the policy for Go itself. See #7249 for more information. (#7250)
- Update x/net/http2 to address CVE-2023-45288 (#7282)
Behavior Changes
- credentials/tls: clients and servers will now reject connections that don't support ALPN when environment variable
GRPC_ENFORCE_ALPN_ENABLEDis set to "true" (case insensitive). (#7184)
- NOTE: this behavior will become the default in a future release.
- metadata: remove String method from MD to make printing more consistent (#7373)
New Features
- grpc: add
WithMaxCallAttemptsto configure gRPC's retry behavior per-channel. (#7229)
- Special Thanks:
@imoore76Bug Fixes
- ringhash: properly apply endpoint weights instead of ignoring them (#7156)
- xds: fix a bug that could cause xds-enabled servers to stop accepting new connections after handshaking errors (#7128)
- Special Thanks:
@bozaroRelease 1.64.1
Dependencies
- Update x/net/http2 to address CVE-2023-45288 (#7352)
- metadata: remove String method from MD to make printing consistent (#7374)
Release 1.64.0
API Changes
- stats: Deprecate
InPayload.DataandOutPayload.Data; they were experimental and will be deleted in the next release (#7121)Behavior Changes
- codec: Remove handling of environment variable
GRPC_GO_ADVERTISE_COMPRESSORSto suppress setting supported compressors ingrpc-accept-encodingheader. Compressors will always be advertised, as they have been by default for some time (#7203)New Features
- resolver/dns: Add
SetMinResolutionIntervalto set the minimum interval at which DNS re-resolutions may occur (#6962)
- Special Thanks:
@HomayoonAlimohammadi- peer/peer: Implement the
fmt.Stringerinterface for pretty printingPeer, and- metadata/metadata: Implement the
fmt.Stringerinterface for pretty printingMD(#7137)
- Special Thanks:
@AnomalRoilPerformance Improvements
... (truncated)
Commits
2da9769Change version to 1.65.0 (#7306)ede96b7metadata: remove String method (#7373)64be203grpc: Readd pick first name (#7336) (#7341)25e33a6examples: Add CSM Observability example (#7302) (#7318)04a5f46xds/internal/xdsclient: Emit unknown for CSM Labels if not present in CDS (#7...cff5c3estats/opentelemetry: Add e2e testing for CSM Observability (#7279) (#7316)9b970fddns: fix constant 30s backoff for re-resolution (#7262) (#7311)6d23620documentation: on server, use FromIncomingContext for retrieving context and...7e5898exds: unify xDS client creation APIs meant for testing (#7268)5d7bd7ainterop/xds: Interop client and server changes for CSM Observability (#7280)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign mukhoakash for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
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-sigs/prow repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten