Update status of GrpcWeb filter

dimo414 commented 1 year ago

https://www.envoyproxy.io/docs/envoy/v1.27.0/intro/arch_overview/other_protocols/grpc says:

gRPC-Web is supported by a filter that allows a gRPC-Web client to send requests to Envoy over HTTP/1.1 and get proxied to a gRPC server. It’s under active development and is expected to be the successor to the gRPC bridge filter.

This seems to imply that a) the GrpcWeb filter is not production-ready yet and b) the grpc_http1_bridge filter should be used in the meantime.

A number of external examples, notably grpc/grpc-web use the GrpcWeb filter, suggesting that it is production ready.

It would be helpful if the Envoy documentation could:

Clarify the "active development" status of the gRCP-web filter, ideally linking to a tracking issue or similar resource
Clarify the "production-ready" status of the gRPC-web filter, namely whether "expected to be the successor" is still correct
Draw a clearer distinction between the two filters, notably what the gRPC-web filter does that the bridge filter does not (or vice versa), and clarifying whether the bridge filter needs to be used alongside the gRPC-web filter in any circumstances, or if the latter is a strict superset of functionality

alyssawilk commented 1 year ago

@phlax I don't know the answer to these, but any chance you can poke around on maintainers/dev for answers and help clean up the docs?

phlax commented 1 year ago

happy to update/review docs

i guess the first thing is confirming validity of these statements

is expected to be the successor to the gRPC bridge filter.

This seems to imply that a) the GrpcWeb filter is not production-ready yet and b) the grpc_http1_bridge filter should be used in the meantime.

cc @jose @mattklein123 @zuercher as related code owners

github-actions[bot] commented 11 months ago

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

dimo414 commented 11 months ago

Bump

github-actions[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

dimo414 commented 10 months ago

Can we please not close this issue as stale just because it's not being acted on?

envoyproxy / envoy

Update status of GrpcWeb filter #29805