Round Robin for gRPC (nodejs) on kubernetes with headless service
After diving deep into Grpc-c core code and the nodejs adapter I found that it works by using the option key "grpc.lb_policy_name"
. Therefore, constructing the gRPC client with
new Client(address, credentials, {"grpc.lb_policy_name": "round_robin"})
works.Note that in my original question I also used round-robin
instead of the correct round_robin
I am still not completely sure how to set the serviceConfig
from the service side with nodejs instead of using client (channel) option override.