Shahwar Saleem
07/06/2022, 7:04 PMroot@60d7613e13ff:/workflows# flytectl create project --name flyte-project --id flyte-project --description "example flyte-project description" --labels app=flyte
Error: rpc error: code = Unavailable desc = connection closed
My flyte/config.yaml points to latest endpoint for my deployment.katrina
Katrina P
07/06/2022, 9:06 PMkatrina
logger.yaml: |
logger:
show-source: true
level: 6 # Debug
Katrina P
07/06/2022, 9:15 PMHaytham Abuelfutuh
<http://k8s-flyte-8699360f2e-1590325550.us-east-2.elb.amazonaws.com|k8s-flyte-8699360f2e-1590325550.us-east-2.elb.amazonaws.com>
) is generated by the ingress controller (which ingress controller are you using)?
If you want to use your own SSL certs, you need to fill in this host field <https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values.yaml#L343>
and setup SSL issuance to properly do that (if you use cert-manager operator, it should happen automatically)…Shahwar Saleem
07/06/2022, 9:22 PMkubectl -n ssaleem-flyte get ingress
?Haytham Abuelfutuh
Shahwar Saleem
07/06/2022, 9:38 PMflytectl create project --name flyte-project --id flyte-project --description "example flyte-project description" --labels app=flyte
And getting :
Error: rpc error: code = Unavailable desc = name resolver error: produced zero addresses
My hosts in kubectl -n ssaleem-flyte get ingress
command are:
<http://flytedev.x.y.z.io|flytedev.x.y.z.io>
host
value according to what my certificate allows: I am now not even able to access console on the supposed host value. say <http://flytedev.x.y.z.io|flytedev.x.y.z.io>
Haytham Abuelfutuh
Shahwar Saleem
07/06/2022, 10:04 PMHaytham Abuelfutuh
Shahwar Saleem
07/06/2022, 10:08 PMHaytham Abuelfutuh
Shahwar Saleem
07/06/2022, 10:20 PM<http://flytedev.x.y.z.io|flytedev.x.y.z.io>
?Haytham Abuelfutuh
secretName
)Shahwar Saleem
07/07/2022, 3:36 PMseparateGrpcIngressAnnotations:
<http://alb.ingress.kubernetes.io/backend-protocol-version|alb.ingress.kubernetes.io/backend-protocol-version>: HTTP2
To:
separateGrpcIngressAnnotations:
<http://alb.ingress.kubernetes.io/backend-protocol-version|alb.ingress.kubernetes.io/backend-protocol-version>: GRPC
These annotations do nothing and can be removed:
<http://nginx.ingress.kubernetes.io/app-root|nginx.ingress.kubernetes.io/app-root>: /console
<http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: GRPC
Haytham Abuelfutuh
``` nginx.ingress.kubernetes.io/app-root: /console
nginx.ingress.kubernetes.io/backend-protocol: GRPC```These are only respected when you deploy nginx… we tried to set the default annotations to work with either so they require less after-deployment changes. CC @Yee @Yuvraj @Brian Connolly
Shahwar Saleem
07/13/2022, 4:23 PMKetan (kumare3)