Tyk OSS - Routing Issues with Multiple gRPC Backends (helloworld & route_guide)

[Duke_C]

I’m trying to set up a test environment with Tyk OSS as a gRPC proxy for two gRPC backends: helloworld and route_guide from the grpc-go examples.

The setup works perfectly when using only the helloworld backend. However, once I add the route_guide backend, the gateway stops routing any requests.
I’ve tried configuring the “listen_path” for both services in various ways, but haven’t been successful.

Has anyone encountered this issue with multiple gRPC backends in Tyk OSS? Any insights or suggestions would be greatly appreciated.

[Olu]

@Duke_C

I’ve tried configuring the “listen_path” for both services in various ways, but haven’t been successful.

Is there any specific error you observe from the gateway logs when log_level config property is set to debug?

@Duke_C

Has anyone encountered this issue with multiple gRPC backends in Tyk OSS? Any insights or suggestions would be greatly appreciated.

I vaguely remember an issue where you had to use a unique port or something like that for each API definition.

[Duke_C]

After some trial and error, I found that "listen_path"s need to be specified correctly in the proxy settings. Additionally, there can only be one gRPC backend with “/” as the “listen_path” . This particular gRPC backend can support gRPC reflection.