Do we have a plan to move etcd3 grpc-gateway out of alpha?

[realityone]

Hi there,

We are using etcd and python to build our applications. In etcd2, everything works fine. But etcd3 using gRPC as the original way. Cause python2 grpcio is incompatible with gevent, so we plan to using the etcd3 grpc-gateway in our applications.

But I aware that the API is prefixed with /v3alpha. And I checked the roadmap, nothing about the grpc-gateway.

I'm curious do we have a plan to move etcd3 grpc-gateway out of alpha? Or this will always be an alpha feature?

Any help would be appreciated.

Reference:

• gevent compatibility grpc/grpc#4629
• Failed to run with gRPC-python gevent/gevent#938
• GRPC compatibility gevent/gevent#786
• v0.25.0 with grpcio==1.3.5 hangs in completion_queue.poll() googleapis/google-cloud-python#3450

[zyf0330]

@realityone When you say do we have a plan ..., I guess you are Chinese like me.😂

[gyuho]

We will add /v3beta routes with same handler for safe upgrades in v3.3, while keeping /v3alpha paths.

[raoofm]

@gyuho any timeline for /v3. I mean are there any tasks remaining to mark it as stable?

[xiang90]

@raoofm we just fixed the bi-streaming endpoint. need to do a new beta release to encourage people to try it out. if there is nothing comes out for the next release, we will bump it to stable.

[gyuho]

We've just changed /v3alpha to /v3beta in master branch, while keeping /v3alpha endpoints with HTTP redirects. Will be included in our upcoming 3.3 release.