#4794 [BUG] pyflyte run does not work with self-signed certificates Issue created by kdubovikov ### Describe the bug I am using self-signed certificate for exposing HTTPS Flyte GRPC endpoint on a EKS cluster. My certificate request is the following:

[req]
distinguished_name = req_distinguished_name
x509_extensions = v3_req
prompt = no
[req_distinguished_name]
C = US
ST = WA
L = Seattle
O = Flyte
OU = IT
CN = <http://something.com|something.com>
emailAddress = <mailto:kdubovikov@something.com|kdubovikov@something.com>
[v3_req]
keyUsage = keyEncipherment, dataEncipherment, digitalSignature
extendedKeyUsage = serverAuth
subjectAltName = @alt_names
[alt_names]
DNS.1 = <http://something.com|something.com>

I can not use real endpoint in

CN

since it's way larger than 64 symbols. My config is:

admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///XXXXX
  authType: Pkce
  insecure: false
  insecureSkipVerify: true
logger:
  show-source: true
  level: 6

Whenever I am trying to run a remote workflow, I get an error:

pyflyte run --remote -p poc -d development ./workflows/poc.py wf                                                          
Running Execution on Remote.
Failed with Exception Code: SYSTEM:Unknown
RPC Failed, with Status: StatusCode.UNAVAILABLE
	details: failed to connect to all addresses; last error: UNKNOWN: ipv4:XX.XX.XX.XX:443: Peer name <http://internal-k8s-flyte-XXXX-XXXX.ap-south-1.elb.amazonaws.com|internal-k8s-flyte-XXXX-XXXX.ap-south-1.elb.amazonaws.com> is not in peer certificate
	Debug string UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:XX.XX.XX.XX:443: Peer name <http://internal-k8s-flyte-XXXXX-XXXX.ap-south-1.elb.amazonaws.com|internal-k8s-flyte-XXXXX-XXXX.ap-south-1.elb.amazonaws.com> is not in peer certificate", grpc_status:14, created_time:"2024-01-30T20:19:10.206646+04:00"}

### Expected behavior Pyflyte runs the workflow on a remote cluster ### Additional context to reproduce No response ### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte