hey folks! I’ve got my

pyflyte run ./hello-world.py wf

running locally and I’d like to run it on my K8s cluster but using the

--remote

results in a

Peer name <MY-HOSTNAME> is not in peer certificate

Couldn’t find a quick fix for the above. Can I use

flytectl

instead (which seems to be working fine)?

Hi @adventurous-van-8963 what are you using as

endpoint

in your

$HOME/.flyte/config.yaml

file?

hi @average-finland-92144 My config file:

admin:
 endpoint: dns:///<HOSTNAME>
 authType: Pkce
 insecure: false
 insecureSkipVerify: true

The hostname I’m using is reachable via web browser and I can correctly call the HTTP api with

curl -GET '<HOSTNAME>:80/api/v1/active_launch_plans/projectname/development?limit=32&token=32' -H 'accept: application/json'`

but anything grpc fails:

$ pyflyte run --remote --project projectname ./hello-world.py wf
Failed with Exception Code: SYSTEM:Unknown
RPC Failed, with Status: StatusCode.UNAVAILABLE
        details: failed to connect to all addresses; last error: UNKNOWN: ipv4:<MY_IP>:443: Peer name <MY-HOSTNAME> is not in peer certificate
        Debug string UNKNOWN:failed to connect to all addresses; last error: UNKNOWN: ipv4:<MY_IP>:443: Peer name <MY-HOSTNAME> is not in peer certificate {created_time:"2023-08-15T08:05:12.40278902+00:00", grpc_status:14}

@adventurous-van-8963, can you take a look at this Slack thread? https://www.linen.dev/s/flyte-org/t/12033777/dear-all-i-ran-into-an-inconsistency-between-flytectl-and-fl#f860a21a-e4b7-4d83-9061-335ce17dd785