#2993 [Housekeeping] Flyte Deployment journey and documentation Issue created by wild-endeavor Revamp Flyte Deployment This ticket encompasses all the work for revamping the Flyte deployment journey. Specifically this covers • Updates to the flyte sandbox-lite image • Changes to flytectl • Documentation updates • Helm chart updates More information to follow. Flyte Local Demo Experience • Persist state to user's local workstation • Run a registry so we can deprecate the --source flag • Preload images New local demo sandbox After this PR is merged, we will have the following structure. Helm • A Helm chart just for the Flyte single binary. • A Helm chart for the sandbox that uses the Flyte single binary Helm chart and pulls in the open source Helm charts for dependencies (like minio/postgres) Images • New bundled image will be created. This is the core of the new experience. It will contain • predownloaded images for all the dependencies including the flyte binary itself. • a registry so that the

--source

flag in flytectl is no longer necessary. Flytectl • Allow users to start with an external flyte config • Allow users to modify a config and reload • Print current state of cluster Docs Implement the new user journey, moving the more difficult error prone things like auth and ingress to later stages. Helm Refactor and introduce new Helm charts that use the single binary. Misc Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte