Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

New RunLLM response generated:

>>>*# Question*
Wondering, ALB ingress redirection is working for anyone. `<http://alb.ingress.kubernetes.io/actions.app-root|alb.ingress.kubernetes.io/actions.app-root>: '{"Type": "redirect", "RedirectConfig":  {"Path": "/console", "StatusCode": "HTTP_302"}}'`
*# Answer*
Yes, ALB ingress redirection is configured and working for Flyte deployments. The annotation `alb.ingress.kubernetes.io/actions.app-root` is used to redirect traffic to a specific path, in this case, `/console`, with a status code of `HTTP_302`. This configuration is present in both the <https://github.com/flyteorg/flyte/blob/master/charts/flyte-binary/eks-starter.yaml|eks-starter.yaml> and <https://github.com/flyteorg/flyte/blob/master/charts/flyte-binary/eks-production.yaml|eks-production.yaml> files.

Would you like more details on how to set this up or troubleshoot any issues you are facing?

Sources:
- <https://github.com/flyteorg/flyte/blob/master/charts/flyte-binary/eks-starter.yaml|eks-starter.yaml>
- <https://github.com/flyteorg/flyte/blob/master/charts/flyte-binary/eks-production.yaml|eks-production.yaml>

*Slack Link*
https://flyte-org.slack.com/archives/CP2HDHKE1/p1718750797.043169 :+1: 0 button :-1: 0 button 💡 *Hint:* Mention @runllm in the thread for followups.