chore: bump google.golang.org/grpc from 1.62.1 to 1.74.2 in /test/e2eprovider

[dependabot]

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

Release notes

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

Release 1.74.2

API Changes

• balancer: add ExitIdle method to Balancer interface. Earlier, implementing this method was optional. (#8367)

Behavior Changes

• xds: Remove the GRPC_EXPERIMENTAL_ENABLE_LEAST_REQUEST environment variable that allows disabling the least request balancer with xDS. Least request was made available by default with xDS in v1.72.0. (#8248)
  • Special Thanks: @​atollena
• server: allow 0s grpc-timeout header values, which older gRPC-Java versions could send. This restores the behavior of grpc-go before v1.73.0. (#8439)

Bug Fixes

• googledirectpath: avoid logging the error message Attempt to set a bootstrap configuration... when creating multiple directpath channels. (#8419)

Performance Improvements

• transport: reduce heap allocations by pooling objects and avoiding method-to-closure conversions. (#8361)
• transport: reduce heap allocations by re-using mem.Reader objects. (#8360)

Documentation

• examples: add examples to demonstrate enabling experimental metrics using the OpenTelemetry plugin. (#8388)
  • Special Thanks: @​vinothkumarr227

Release 1.74.1

Version 1.74.1 retracts release v1.74.0 and itself. Release 1.74.0 was accidentally tagged on the wrong commit and should not be used. Version 1.73.0 should be used until 1.74.2 is released.

Release 1.74.0 was accidentally tagged on the wrong commit and should not be used. Version 1.73.0 should be used until 1.74.1 is released.

Release 1.73.0

New Features

• balancer/ringhash: move LB policy from xds/internal to exported path to facilitate use without xds (#8249)
• xds: enable least request LB policy by default. It can be disabled by setting GRPC_EXPERIMENTAL_ENABLE_LEAST_REQUEST=false in your environment. (#8253)
• grpc: add a CallAuthority Call Option that can be used to overwrite the http :authority header on per-RPC basis. (#8068)
• stats/opentelemetry: add trace event for name resolution delay. (#8074)
• health: added List method to gRPC Health service. (#8155)
  • Special Thanks: @​marcoshuck
• ringhash: implement features from gRFC A76. (#8159)
• xds: add functionality to support SPIFFE Bundle Maps as roots of trust in XDS which can be enabled by setting GRPC_EXPERIMENTAL_XDS_MTLS_SPIFFE=true. (#8167, #8180, #8229, #8343)

Bug Fixes

• xds: locality ID metric label is changed to make it consistent with gRFC A78. (#8256)
• client: fail RPCs on the client when using extremely short contexts that expire before the grpc-timeout header is created. (#8312)
• server: non-positive grpc-timeout header values are now rejected. This is consistent with the gRPC protocol spec. (#8290)
  • Special Thanks: @​evanj
• xds: fix reported error string when LRS load reporting interval is invalid. (#8224)
  • Special Thanks: @​alingse

... (truncated)

Commits

• e9e00cb Change version to 1.74.2 (#8470)
• bd7cb0a Change version to 1.74.2-dev (#8461)
• 002a22c Change version to 1.74.1 (#8455)
• 6e8e7e4 Retract v1.74.0 and v1.74.1 (#8457)
• 48c9e4d Change version to 1.74.1-dev (#8408)
• b8b6cff Change version to 1.74.0 (#8407)
• 077e2c3 Cherry-pick #8411, #8419, #8422, #8445 and #8451 to v1.74.x (#8454)
• b34f845 server: allow 0s grpc-timeout header values, as java is known to be able to s...
• 1787f94 xdsclient: export genericResourceTypeDecoder (#8406)
• 15299cc xdsclient: make a function to return the supported resource type implementati...
• 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]

[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 ritazh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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]

This issue is currently awaiting triage.

If secrets-store-csi-driver contributors determine 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-sigs/prow repository.

[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-sigs/prow repository.

[k8s-ci-robot]

@dependabot[bot]: 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-secrets-store-csi-driver-e2e-vault	e84eff5	link	true	/test pull-secrets-store-csi-driver-e2e-vault
pull-secrets-store-csi-driver-e2e-provider-k8s-1-30-10	e84eff5	link	true	/test pull-secrets-store-csi-driver-e2e-provider-k8s-1-30-10
pull-secrets-store-csi-driver-e2e-aws	e84eff5	link	false	/test pull-secrets-store-csi-driver-e2e-aws
pull-secrets-store-csi-driver-e2e-deploy-manifest-e2e-provider	e84eff5	link	false	/test pull-secrets-store-csi-driver-e2e-deploy-manifest-e2e-provider
pull-secrets-store-csi-driver-image-scan	e84eff5	link	false	/test pull-secrets-store-csi-driver-image-scan
pull-secrets-store-csi-driver-e2e-provider-k8s-1-31-6	e84eff5	link	true	/test pull-secrets-store-csi-driver-e2e-provider-k8s-1-31-6
pull-secrets-store-csi-driver-lint	e84eff5	link	true	/test pull-secrets-store-csi-driver-lint
pull-secrets-store-csi-driver-e2e-azure	e84eff5	link	true	/test pull-secrets-store-csi-driver-e2e-azure

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

[dependabot]

Superseded by #1899.