Open psalaberria002 opened 5 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Should not be closed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still an issue.
jumping on board, too. I'm quite surprised that it doesn't seem to be (officially) supported yet.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
should not be closed
Pinning this so it won't go stale again. @psalaberria002, the http2_protocol_options
is currently the only thing the grpc
flag affects, but... yeah, I hear you, it's not the Right Way™ to manage that.
It appears we forgot to reopen it along with pinning 🙂
Please describe your use case / problem. In Envoy it is possible to set
alpn_protocols: h2
for upstream services so the connections are HTTP/2. For that to workhttp2_protocol_options
must be set as explained in https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cds.proto#cluster .I noticed that the grpc flag in the Mappings sets
http2_protocol_options
already, but my service is not grpc, and it seems hacky to abuse the flag for making HTTP/2 work :) See https://github.com/datawire/ambassador/blob/4b57121fdf8289f0baa71de6dc9d4d94e486b49c/python/ambassador/envoy/v2/v2cluster.py#L67-L68Describe the solution you'd like If
alpn_protocols
containsh2
,http2_protocol_options
should be set in the cluster config. I assume thegrpc
flag does more than just setting that field in the configs.