Also to clarify it some more: The list of services known can change during runtime. So I would need to keep the DNS zone file always updated to include my endpoints and also add SRV records for the load balancer. This should definetly be doable using coreDNS, automatically updating the Corefile and reloading it, but since my process includes the GRPCLB service and that one already knows the endpoints, it would be a huge workaround including more tools than needed... Since all modules managed by one process share the same load balancer, I would prefer to just address the GRPCLB service directly instead of it being looked up from the SRV record for the original target. So the goal is a bit different from what gRFC A5 targeted.
So all my endpoints sharing one GRPCLB run in one process. The GRPCLB endpoint (IP + Port) is fix, the services hosted by the process choose free ports on startup and can change, why I want to use endpoint names to address the services when talking to them from a different service (outside from this process and most commonly on another machine). -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/ec140932-956e-4bae-927a-d2be1f018d86%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
