-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Stabilize gRPC gateway (/v3beta) #9189
Comments
@gyuho I am a user of gRPC gateway and would love to see it stable /v3. Will try my best to support/improve. |
@hexfusion Thanks! Reference when bumping up to |
the thing i worry about is that gRPC web is probably going to release soon. it can be the "official" way to expose gRPC service in JSON format. |
@xiang90 does it make sense to make /v3 stable with grpc-gateway then look at grpc/grpc#8682 for /v4? Replacing seems a fair bit of work :). |
We will double-check with gRPC team. |
I got the ball rolling here a little. |
this is the gRPC web issue: grpc/grpc#8682. It is an official gRPC support instead of the one from improbable. |
I see thanks. |
@hexfusion No, but seems like it should be out in a few weeks? |
I asked for early access to get a feel for how this will look. |
@gyuho @xiang90
Being that it has a Nginx/Envoy dependency currently I do not see this becoming a short term alternative to grpc-gateway. A side car approach could be possible allowing maybe etcd-operator more reasonable support via Kubernetes. But still a ways off it seems for direct Go implimentation from gRPC team? |
OK. It seems like gRPC-web really only focuses on the |
@hexfusion @xiang90 Sounds good. People already depend on our current grpc-gateway anyway. |
Understood grpc-gateway /v3 ahead! |
Going to start on this tonight. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
gRPC gateway serves
/v3beta
, should be ready as/v3
Reference #9064.
Not much to do here. Just trouble-shoot any issues that may come up. Or add any missing tests. And bump up endpoint to
v3
before 3.4 release.@hexfusion Do you want to work on this?
The text was updated successfully, but these errors were encountered: