Hi Julien, The reflection service were exposed at each backend. We currently don't have a way assign the backend reflection service that should be connected to at gRPC level.
Thanks, Yuchen On Tuesday, November 14, 2017 at 11:14:19 PM UTC-8, [email protected] wrote: > > Hello, > > We have a thread open on grpc reflection on routing with service mesh > (Istio in our case). Does someone could have a look on it? > > > https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/istio-users/lwbuHJGZt90 > > Thanks a lot, > > On Monday, November 13, 2017 at 11:23:49 PM UTC+1, [email protected] > wrote: >> >> Hello, >> >> We want to implement routing table with server reflection on our micro >> service. Because server reflection ( >> https://github.com/grpc/grpc/blob/master/doc/server-reflection.md >> use same package.service / Method, how we can write rules to redirect to >> dedicated backend micro service, Do I have to implement HostPrefix and >> PathPrefix routes on service mesh control plane (linkerd or Istio)? or >> do I have to find something like LB lookaside ( >> https://grpc.io/blog/loadbalancing) ? >> >> Thanks >> > -- 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/dc023ca1-86db-423f-825a-2e3d6df0cf24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
