damp-potato-83989
05/30/2023, 3:19 PMaverage-finland-92144
05/30/2023, 3:57 PMflyte-binary
chart version using ALB:
https://github.com/davidmirror-ops/flyte-the-hard-way/blob/main/docs/08-adjust-values-upgrade-Helm.mdfreezing-boots-56761
damp-potato-83989
05/30/2023, 3:58 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:01 PMdamp-potato-83989
05/30/2023, 4:02 PMdamp-potato-83989
05/30/2023, 4:03 PMfreezing-boots-56761
<http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn>: '<ARN>'
<http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>: '[{"HTTPS":443}]'
<http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>: internal
<http://alb.ingress.kubernetes.io/ssl-redirect|alb.ingress.kubernetes.io/ssl-redirect>: '443'
<http://alb.ingress.kubernetes.io/target-type|alb.ingress.kubernetes.io/target-type>: ip
<http://alb.ingress.kubernetes.io/backend-protocol-version|alb.ingress.kubernetes.io/backend-protocol-version>: GRPC
<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: alb
for just the GRPC ingress? the HTTP endpoints should be in a different ingressdamp-potato-83989
05/30/2023, 4:18 PMfreezing-boots-56761
<http://alb.ingress.kubernetes.io/backend-protocol|alb.ingress.kubernetes.io/backend-protocol>: HTTP
freezing-boots-56761
<http://alb.ingress.kubernetes.io/ssl-redirect|alb.ingress.kubernetes.io/ssl-redirect>: '443'
in there for parity, but not sure its necessary since you are only listening on 443damp-potato-83989
05/30/2023, 4:22 PMdamp-potato-83989
05/30/2023, 4:23 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:38 PMfreezing-boots-56761
freezing-boots-56761
kubectl get ingress
freezing-boots-56761
damp-potato-83989
05/30/2023, 4:41 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:43 PMfreezing-boots-56761
freezing-boots-56761
kubectl get ingress
are the ALB addresses different?damp-potato-83989
05/30/2023, 4:48 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:49 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:49 PMdamp-potato-83989
05/30/2023, 4:49 PMfreezing-boots-56761
<hostname>:443
were you using the ALB address or your internal hostname?damp-potato-83989
05/30/2023, 4:50 PMdamp-potato-83989
05/30/2023, 4:51 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 4:51 PMdamp-potato-83989
05/30/2023, 4:53 PMkubectl get ingress
for the grpc is port 80. I would think it should be port 443?damp-potato-83989
05/30/2023, 4:54 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 5:09 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 5:12 PMfreezing-boots-56761
freezing-boots-56761
flytectl get project --admin.endpoint=<hostname>:443
damp-potato-83989
05/30/2023, 5:17 PMfreezing-boots-56761
freezing-boots-56761
localhost:8089
damp-potato-83989
05/30/2023, 5:20 PMfreezing-boots-56761
freezing-boots-56761
damp-potato-83989
05/30/2023, 5:21 PMfreezing-boots-56761
freezing-boots-56761
damp-potato-83989
05/30/2023, 5:22 PMdamp-potato-83989
05/30/2023, 5:22 PMfreezing-boots-56761
server does not support the reflection API
suggests there are reflection specific methods, perhaps?freezing-boots-56761
freezing-boots-56761
grpc.reflection.v1alpha.ServerReflection
damp-potato-83989
05/30/2023, 5:26 PMdamp-potato-83989
05/30/2023, 5:27 PMfreezing-boots-56761
freezing-boots-56761
damp-potato-83989
05/30/2023, 5:27 PMdamp-potato-83989
05/30/2023, 5:28 PMfreezing-boots-56761
> docker run fullstorydev/grpcurl -v -plaintext host.docker.internal:8089 list
flyteidl.service.AdminService
flyteidl.service.AuthMetadataService
flyteidl.service.DataProxyService
flyteidl.service.IdentityService
flyteidl.service.SignalService
grpc.health.v1.Health
grpc.reflection.v1alpha.ServerReflection
damp-potato-83989
05/30/2023, 5:30 PMdamp-potato-83989
05/30/2023, 5:30 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 5:35 PMfreezing-boots-56761
damp-potato-83989
05/30/2023, 5:38 PMfreezing-boots-56761