We are deploying Flyte this week 🎉 Main pieces are running but configuration needs some adjustments. I have one question regarding TLS certificates. Is it required for grpc/flytectl to set up TLS on the Flyte endpoint? I get the following error with the current config. Is it only due to missing tls configuration or other reasons?

flytectl get projects   
Error: Connection Info: [Endpoint: dns:///flyte.internal.n0q.eu, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = timed out waiting for server handshake
{"json":{},"level":"error","msg":"Connection Info: [Endpoint: dns:///flyte.internal.n0q.eu, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = timed out waiting for server handshake","ts":"2022-11-08T16:12:04+01:00"}

#~/.flyte/config.yaml
admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///flyte.internal.eu
  insecure: true
  insecureSkipVerify: true

It’s not required but http2 does not like no TLS

Pasted the wrong error message, changed that now. So, is there a way to avoid the error or is it best to just configure tls?

This error is still weird

Authentication was not enabled, we are working on that today.

Cc @Katrina P / @Xuan Hu more deployment fun