[v2] Bundle UI deployment in helm chart & Devbox

[EngHabu]

Motivation: Why do you think this is important?

N/A

Goal: What should the final outcome look like, ideally?

N/A

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

It seems likely that bundling the Flyte UI (Console) deployment into the Helm chart and Devbox would streamline deployment and make it easier to manage and update the UI alongside other Flyte components. The Flyte Helm charts already include deployment templates for the Flyte Console, as seen in the EKS and sandbox Helm-generated YAML files, which define the console as a Kubernetes Deployment and Service within the chart structure. This suggests that the UI is already part of the standard Helm deployment process for Flyte, at least for the core and sandbox charts, and is managed as a component within the overall Flyte stack. There is no explicit mention of Devbox integration in the provided sources.

If you want more detail on how the UI is bundled or how to customize its deployment in Helm or Devbox, let me know.

Sources:

• flyte_helm_controlplane_generated.yaml

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[ankitkumarsingh1702]

@EngHabu Can i pick this