---
# System prepended metadata

title: Flyte Deployment Experience - Martin

---

# Flyte Deployment Experience - Martin

Ended up w/:
* Cluster with 3 machines running on EKS,
* Contour URL? What's that. Referenced in the docs for the first time without explaining,
* Followed Opta deployment,

Goal 2:
* On prem deployment is completely not documented.
* Tried to use Kind instead of k3s for sandbox deployment,
* Haven't used k3s, kind... etc. before.
* Multi-machine deployment using K3s is not documented.

Journey:
* Flyte.org navigation -> Get started
* [ ] Should mention whether a venv is required or not
* Getting Started -> next is Concepts but that's the very right most menu item.
* Concepts page is just too big to for people to expect to read after getting started
* [ ] Next should take you to user guide probably...
* [ ] The flow should be:
    * [ ] Local/Python only... (Getting Started)
    * [ ] Prod cluster
    * [ ] Run python against that prod cluster
* Edited Opta env.yaml 
* Ran opta apply
* [ ] Doesn't tell you how to get opta output to get IPs... etc.
* [ ] Docs should tell you "you are not ready to use the cluster" [after running opta apply](https://docs.flyte.org/en/latest/deployment/aws/opta.html#deployment-aws-opta)... and clarify that Auth... etc. are optional.
* [ ] [This doc](https://docs.flyte.org/en/latest/deployment/sandbox.html) mentions Contour_URL with no mention of how to get that
* On a brand new machine, trying opta fails because helm charts are not installed?
* [ ] How to tear down the resources
* [ ] Add time-expectation everywhere
* [ ] Add a deployment video