cool-lifeguard-49380
06/28/2023, 4:01 PMcool-lifeguard-49380
06/28/2023, 4:01 PM❯ pyflyte run --remote wf.py wf
Failed with Exception Code: SYSTEM:Unknown
RPC Failed, with Status: StatusCode.UNAVAILABLE
details: failed to connect to all addresses; last error: INTERNAL: ipv4:104.xxx:443: Trying to connect an http1.x server
Debug string UNKNOWN:failed to connect to all addresses; last error: INTERNAL: ipv4:104.198.187.232:443: Trying to connect an http1.x server {created_time:"2023-06-28T18:01:30.030524+02:00", grpc_status:14}
The nginx controller shows this log line for this request:
10.xxx - - [28/Jun/2023:16:01:30 +0000] "PRI * HTTP/2.0" 400 150 "-" "-" 0 0.132 [] [] - - - - fb2516a8919e168c4a8ef36f31f3945acool-lifeguard-49380
06/28/2023, 4:02 PMadmin:
endpoint: dns:///<my-domain>.com
insecure: true
insecureSkipVerify: true
logger:
show-source: true
level: 0
storage:
type: stow
stow:
kind: google
config:
json: ""
project_id: <my-gcp-project-id>
scopes: https://www.googleapis.com/auth/devstorage.read_writecool-lifeguard-49380
06/28/2023, 4:03 PMcommon:
ingress:
host: "{{ .Values.userSettings.hostName }}"
tls:
enabled: true
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/ssl-redirect: "true"
cert-manager.io/issuer: "letsencrypt-prod"
separateGrpcIngress: true
separateGrpcIngressAnnotations:
nginx.ingress.kubernetes.io/backend-protocol: "GRPC"cool-lifeguard-49380
06/28/2023, 4:03 PMcool-lifeguard-49380
06/28/2023, 4:04 PMaverage-finland-92144
06/28/2023, 4:42 PMinsecure and insecureSkipVerify set to true have an effect.
What if you set
insecure: false?fancy-plumber-70674
06/29/2023, 3:33 AMingress:
create: true
host: customhostname.com
httpAnnotations:
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}, {"HTTP":80}]'
alb.ingress.kubernetes.io/certificate-arn:
alb.ingress.kubernetes.io/ssl-policy: ELBSecurityPolicy-TLS-1-1-2017-01 #Optional (Picks default if not used)
alb.ingress.kubernetes.io/ssl-redirect: '443'
alb.ingress.kubernetes.io/group.name: flyte
alb.ingress.kubernetes.io/group.order: '10'
grpcAnnotations:
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/backend-protocol: HTTP
alb.ingress.kubernetes.io/backend-protocol-version: GRPC
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]'
alb.ingress.kubernetes.io/certificate-arn:
alb.ingress.kubernetes.io/ssl-policy: ELBSecurityPolicy-TLS-1-1-2017-01
alb.ingress.kubernetes.io/group.name: flyte
alb.ingress.kubernetes.io/group.order: '20'
Just an example of our ingress setup on the flyte-binary helm chart. Hopefully this will shed some light on your issuecool-lifeguard-49380
06/29/2023, 2:33 PMinsecure: false, thanks @average-finland-92144! I could have sworn this flag controlled whether auth is used or not 🤦♂️cool-lifeguard-49380
06/29/2023, 2:33 PMaverage-finland-92144
06/29/2023, 2:34 PMcool-lifeguard-49380
06/29/2023, 2:34 PM