Ambassador: Users want first-class gRPC mappings in Ambassador

[kflynn]

Right now, to fully support gRPC you have to manually translate from gRPC service & method names to Ambassador prefix and rewrite rules, and then you need a separate mapping to support gRPC reflection. That's a little difficult to maintain: we should just allow e.g.

kind: Mapping
grpc: helloWorld.Greeter
reflection: true

or the like.

[cbenien]

I agree. Also if you want to expose multiple GRPC services behind a single Ambassador instance, you can't just set prefix/rewrite rules for the reflection endpoint, because that would only know about one service and not the others.

So +1 for native GRPC server reflection support in Ambassador.

[jekirl]

This would be a great feature. We have many endpoints exposed over grpc so this has been a big pain point for us.