Hello community! I have a question. I'm currently working on a project where we need to programmatically access flyte, and we're using FlyteRemote. At this point, we found that FlyteRemote uses gRPC to connect to flyteAdmin, and in our case, we can't use gRPC due to some limitations in our traffic layer. Alternatively, we found that the resources are also exposed in

/api/v1/

via the REST API. My specific question is whether you have any issues or limitations we should be aware of when using this alternative. Thank you very much.

that is a gRPC gateway

Excuse my technical ignorance, but what's the difference between using flyteRemote or going directly via the API? Reviewing the flyteRemote code, I see that it establishes a grpc channel.

The API offers a rest interface on top of Grpc and ui uses it

Yes, of course. We're currently setting up a cluster with Flyte within GCP, and I'm trying to connect to Ingress via FlyteRemote. I'm currently getting this error:

grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "Socket closed"
debug_error_string = "UNKNOWN: Error received from peer {grpc_message:"Socket closed", grpc_status:14, created_time:"2025-04-08T11:14:27.60937-03:00"}"

I was reviewing this issue https://github.com/grpc/grpc/issues/19954#issuecomment-2468374813, but native GRPC_DNS_RESOLVER isn't working for me.

For me on GCP, it was necessary to register my domain and setup my Ingress to use it as host + tls to connect via FlyteRemote. Then using

FlyteRemote(config=Config(platform=PlatformConfig(endpoint="dns:///my-domain",...)))

should work (note the 3

/

after

dns:

)

Thank you very much for the information @gentle-tomato-480, what ingress did you configure in GCP?

So gcp has support for grpc - that’s not your problem - it’s some setup issue

nginx ingress @billions-hairdresser-78656