The only official way of enabling gRPCLB is, as you found out, as described in the gRFC A5. This could be (locally) hacked up <https://github.com/grpc/grpc/blob/master/src/core/ext/filters/client_channel/client_channel.cc#L410> to forcefully enable gRPCLB, *BUT* wouldn't it be simpler to implement everything at the application level? That is, do all the service discovery on a regular grpc server, process its responses and then proceed. Re-purposing gRPCLB for this end is essentially that, but having to jump through extra hoops to enable it, having to implement an API (load_balancer.proto) that's not exactly designed for your usecase, etc.
On Thursday, 9 November 2017 05:46:49 UTC-8, [email protected] wrote: > > No one working with GRPCLB here? > -- 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/9394f15f-5084-460b-8ee8-6a711906f54f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
