Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi flyte team, I just deployed the flyte core on gcp, and I can access it through public dns. But when I run the submit command from local, it seems like it's expecting the dns is a grpc endpoint, but it turned out to be a http, could you advise? thanks

related stack trace:
```_InactiveRpcError: <_InactiveRpcError of RPC that 
terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; 
last error: INTERNAL: ipv4::443: Trying to 
connect an http1.x server (HTTP status 400)"
        debug_error_string = "UNKNOWN:Error received from
peer  {created_time:"2025-03-05T07:35:19.133308-08:00", 
grpc_status:14, grpc_message:"failed to connect to all 
addresses; last error: INTERNAL: ipv4::443: 
Trying to connect an http1.x server (HTTP status 400)"}"
>```

RuntimeError: Failed to get signed url for
fasta42b517d65b5f56b0dcd51dd2a4b8ea5.tar.gz.

Oscar, can you share your local `config.yaml`? Not sure if this has to do with tls also

I found a post from past with similar issue, i resolved it with something like this:
```admin:
  endpoint: dns:///flyte.clxmedia.com
  authType: Pkce
  insecure: false
  insecureSkipVerify: true
logger:
  show-source: true
  level: 0
~                 ```
not sure if it makes sense to production

if you're using TLS from a trusted CA, you should be able to remove `insecureSkipVerify`

do I need to do anything to get the cert? All I did is to apply the default terraform you provided

when i ran
```kubectl get challenges.acme.cert-manager.io -n flyte```
it's still showing nothing

hm before I go down the route of reproducing this behavior (and assuming you didn't already fix this on your own), is there any certificaterequest created?
`kubectl get certificaterequest -n flyte`

Time it takes for a letsencrypt cert to be generated is not deterministic and sometimes depends on DNS propagation but should eventually work

<@U04H6UUE78B> thanks! it turns out to be a matter of time, now we got the cert, and i can remove that line now