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.

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

More resolvers to support third-party registry #7649

Open
EndlessSeeker opened this issue Sep 19, 2024 · 1 comment
Open

More resolvers to support third-party registry #7649

EndlessSeeker opened this issue Sep 19, 2024 · 1 comment
Assignees
Labels
Status: Requires Reporter Clarification Type: Feature New features or improvements in behavior

Comments

@EndlessSeeker
Copy link

In microservices scenario, in addition to directly accessing services through domain names or k8s svc, they are usually called base on the third-party registration center.
In grpc-go, the appropriate way is to implement a self-defined resolver, the resovler monitor the node updates in the registration center and update the connections.
However, there seems to be no official implementation currently provided. Developers can only develop independently. Can we provide a official plugin library, and the library includes some extension implementations such as resolvers supporting third-party registry? In this way, it improves the convenience for developers to use like me

@EndlessSeeker EndlessSeeker added the Type: Feature New features or improvements in behavior label Sep 19, 2024
@eshitachandwani eshitachandwani self-assigned this Sep 19, 2024
@easwars
Copy link
Contributor

easwars commented Sep 19, 2024

gRPC supports a way to implement custom resolvers. The API is defined in this file here:

type Resolver interface {

The team does not have the time or expertise to implement an official resolver for the use-case that you are asking. But if you want to implement it, please send us a detailed proposal. We can have a discussion and then move towards an implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Requires Reporter Clarification Type: Feature New features or improvements in behavior
Projects
None yet
Development

No branches or pull requests

3 participants