You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently custom registry (specified by server.WithRegistry(r)) always get the listen address, even if a registry.Info with Addr set is specified by server.WithRegistryInfo.
But there are cases that the listen address is not accessible from the client. For example, the client might need to use the public IP addresss, which is usually different with the listen address.
registry-etcd solved this with the workaround of manually specifying the public address when initializing the registry, which does not applicable to other registries (for now).
In this proposal, we suggest adding another option to the registry.Info instructing Kitex server to pass the real address to custom registries, which solves this issue for all existing implementations like registry-nacos.
If you are interested in implementing this feature, please kindly prepare a detailed tech plan and reply with your lark id for us.
The text was updated successfully, but these errors were encountered:
Currently custom registry (specified by
server.WithRegistry(r)
) always get the listen address, even if aregistry.Info
withAddr
set is specified byserver.WithRegistryInfo
.But there are cases that the listen address is not accessible from the client. For example, the client might need to use the public IP addresss, which is usually different with the listen address.
registry-etcd solved this with the workaround of manually specifying the public address when initializing the registry, which does not applicable to other registries (for now).
In this proposal, we suggest adding another option to the
registry.Info
instructing Kitex server to pass the real address to custom registries, which solves this issue for all existing implementations like registry-nacos.If you are interested in implementing this feature, please kindly prepare a detailed tech plan and reply with your lark id for us.
The text was updated successfully, but these errors were encountered: