-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate GRPC-Web/JSON support in Ambassador #456
Comments
See issue #411 |
Is this targeted for a particular release? Would be good to have this. |
Is this issue also tracking using gRPC-web with binary wire format (as opposed to JSON), which is enabled in Envoy with this filter? |
For what it's worth, I'm very interested to see Ambassador support this as well. I'm sure you're already aware of the support that's in envoy already. Not sure how hard it would be to have Ambassador support a configuration similar to this one. Is it just an issue of wrapping envoy configuration correctly or does it go deeper than that? I'm bleeding new to both Ambassador and Envoy, but it seems like calling the grpc_web filer is really the only thing missing (unlike the JSON transcoder, it doesn't really have any associated configuration). |
There hasn't been feedback on this. I also want to know the answer to @neilcarpenter 's question and if there is a short-term alternative with little modification that will get it to work. |
@nigeltiany you can build ambassador from sources and replace envoy.j2 with custom one, like here https://github.com/slamdev/catalog/tree/master/infra/ambassador/deploy key parts are: to add grpc_web filter and grpc and cors mappings for the service |
I have built ambassador from that |
@nigeltiany Would love to, although be warned that we've changed things up quite a bit in the (imminent) 0.50 ... so it's possible that your change won't just work in the next release. The current code is on the |
gRPC-Web is supported in 0.52.0. |
For more information, please refer to https://www.envoyproxy.io/docs/envoy/v1.9.0/configuration/http_filters/grpc_web_filter#config-http-filters-grpc-web Thanks to @rotemtam for the original implementation with the gRPC HTTP/1.1 bridge in #1201 for making this so trivial for me to contribute! Implements feature request #456.
For more information, please refer to https://www.envoyproxy.io/docs/envoy/v1.9.0/configuration/http_filters/grpc_web_filter#config-http-filters-grpc-web Thanks to @rotemtam for the original implementation with the gRPC HTTP/1.1 bridge in #1201 for making this so trivial for me to contribute! Implements feature request #456.
I can see that support for grpc-web transcoder has been implemented but what about grpc-json transcoder ? I am unable to find ambassador documentation regarding this. For more info, have a look at this : https://www.envoyproxy.io/docs/envoy/latest/configuration/http_filters/grpc_json_transcoder_filter |
Not yet. There's an open issue for this I believe @shubhamranjan if you want to contribute a PR! |
@richarddli I would love to contribute. Please lead me to the issue (issue link) for more insights and discussions. I was unable to find the issue. |
Hello, I am looking for grpc-json transcoder support as well. Only found a closed issue #254 and this one. May I know the process of this feature? |
Hi, is there any update on the grpc-json transcoder support? |
A number of users have asked for GRPC-Web/JSON transcoder support in Ambassador. We need to know how to integrate this into Ambassador before we proceed.
CoS
The text was updated successfully, but these errors were encountered: