Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Replacement API for client/v3/naming package to be compatible with new GRPC1.30+ resolver API. #12614

Merged
merged 1 commit into from
Jan 30, 2021
Merged

Replacement API for client/v3/naming package to be compatible with new GRPC1.30+ resolver API. #12614

merged 1 commit into from
Jan 30, 2021

Commits on Jan 30, 2021

  1. Introduce grpc-1.30+ compatible client/v3/naming API. 

    This is not yet implementation, just API and tests to be filled
with implementation in next CLs,
tracked by: etcd-io#12652

We propose here 3 packages:
 - clientv3/naming/endpoints ->
    That is abstraction layer over etcd that allows to write, read &
    watch Endpoints information. It's independent from GRPC API. It hides
    the storage details.

 - clientv3/naming/endpoints/internal ->
    That contains the grpc's compatible Update class to preserve the
    internal JSON mashalling format.

 - clientv3/naming/resolver ->
   That implements the GRPC resolver API, such that etcd can be
   used for connection.Dial in grpc.

Please see the grpc_naming.md document changes & grpcproxy/cluster.go
new integration, to see how the new abstractions work.
    @ptabor
    ptabor committed Jan 30, 2021
    Configuration menu
    Copy the full SHA
    5d7c1db View commit details
    Browse the repository at this point in the history