hi folks, basic question- I have a deployment of flyte running and the user needs to manually navigate to /console to see the UI is there a way to configure flyte to automatically redirect to /console?

If you are running flyte core or flyte binary charts with nginx ingress class, the nginx.ingress.kubernetes.io/app-root is set to /console by default

thanks for the pointer! I don’t think I have nginx-ingress installed at the moment sounds like you’re saying if I install that, it will re-route for me?

Yeah if you install the nginx operator on your k8s cluster or node the operator will recognize your ingress and the app-root annotation will 302 / to /console

another basic k8s question for folks- in the context of flyte, what's the benefit of creating ingress resources rather than directly exposing the

Service

to a load balancer? currently I changed the

service.type

from the default of ClusterIp to

LoadBalancer

which triggers the AWS Load Balancer Controller to deploy an NLB. this approach seems to be working for me at the moment (besides the lack of direct from

/

to

/console

). trying to understand what are the other benefits of specifying every flyte api route in the

Ingress

http.yaml and grpc.yaml files?

If you need to expose multiple services through the same LB (e.g. the same domain).. you will need you setup a proxy (which is what the Ingress Controller will give you).. If you are using flyte-single-binary helm chart. Everything is exposed behind a single K8s service, so you do not need ingress controller. but if you use flyte-core, you deploy each service separately and you need something to route to the right service