https://flyte.org logo
#flyte-deployment
Title
# flyte-deployment
h

Hanno Küpers

11/08/2022, 3:05 PM
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?
Copy code
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
k

Ketan (kumare3)

11/08/2022, 3:10 PM
It’s not required but http2 does not like no TLS
h

Hanno Küpers

11/08/2022, 3:13 PM
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?
k

Ketan (kumare3)

11/08/2022, 10:27 PM
This error is still weird
Authmode is clientsecret
Don you have auth enabled
h

Hanno Küpers

11/09/2022, 9:24 AM
Authentication was not enabled, we are working on that today.
Apparently, it was related to configuration of the load-balancer stripping certificates. Solved now ☺️
k

Ketan (kumare3)

11/17/2022, 3:21 PM
Cc @Katrina P / @Xuan Hu more deployment fun
7 Views