Use case(s) - what problem will this feature solve?
In grpc-go v67, the client will reject servers not advertising ALPN=h2.
Typically, gRPC will automatically set this on the tls.Config passed in on the serverside. However, when GetConfigForClient is used, it will not.
Proposed Solution
Make GetConfigForClient usage automatically set alpn=h2
Alternatives Considered
- Change application to explicitly set ALPN
- Deploy all clients with GRPC_ENFORCE_ALPN_ENABLED=false. This is not great since it will probably go away(?) and you don't always control the clients.
Additional Context
Previous issue, stale-closed: #5814. Likely not a priority since it didn't hurt most users until the client's started denying
Popular projects broken by this:
Use case(s) - what problem will this feature solve?
In grpc-go v67, the client will reject servers not advertising ALPN=h2.
Typically, gRPC will automatically set this on the tls.Config passed in on the serverside. However, when GetConfigForClient is used, it will not.
Proposed Solution
Make GetConfigForClient usage automatically set
alpn=h2Alternatives Considered
Additional Context
Previous issue, stale-closed: #5814. Likely not a priority since it didn't hurt most users until the client's started denying
Popular projects broken by this:
grpc-go >= 1.67.0withALPNdisabled siderolabs/talos#9463