<#3116 Update Administrator docs> Pull request ope...
# flyte-github
a
#3116 Update Administrator docs Pull request opened by wild-endeavor Deployment Documentation Restructure and update some deployment docs. Main changes: • Remove all the cloud specific stuff. • Point users to a newly created GH Discussion topic for submitting articles on deployment experiences. • Use the new
flyte-binary
Helm chart. • Remove a lot of the sandbox stuff since the new
flytectl demo
environment is architected differently. • Change instructions to use
flytectl demo
instead of
flytectl sandbox
• Remove
ideal_flow.rst
- this is incomplete. We should eventually offer some basic gh workflow examples rather than just talking about it. Structure Changes Bundling all Flyte configuration under the deployment moniker felt a bit of a stretch. I think renaming it to a broader administrator's guide makes more sense. • Currently the generated component configs are missing, but this will end up changing with the partial mono-repo work anyways. Deployment Updates One of the things we want to do is change the deployment journey. We want to make sure users are led comfortably through the various stages that one might expect of something as complex as Flyte. Basically the steps of the journey should be 1. flytectl demo sandbox 2. a simple cloud (eks/gke) based deployment with nothing tricky - just helm install. users will have to port-forward to see anything. 3. a production ready deployment (ingress, auth, etc) (think stable enough for most companies). 4. a scalable multicluster setup (lots of deployments will never need this level). The middle steps will replace the aws/gcp guides that we have today. These have been completely deleted. From there we should link to a revamped version of the
ideal_flow.rst
file I think. #2993 flyteorg/flyte ✅ All checks have passed 11/11 successful checks