adventurous-van-8963
08/14/2023, 12:34 PMpyflyte 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)?average-finland-92144
08/14/2023, 4:10 PMendpoint
in your $HOME/.flyte/config.yaml
file?adventurous-van-8963
08/15/2023, 8:09 AMadmin:
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}
tall-lock-23197