# 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
Last changed by  
 
Flyte
Open Source Flyte Team Notes
231

Read more

Flyte Versioning & Planning Updates

Background & Issues This is the current roadmap. The core Flyte maintainers team is proposing some updates to it, specifically to the Milestones and Releases section. We are proposing: Changes to the pace of Flyte releases. Changes to the versioning scheme used across Flyte and its components Updates to the planning process. It has long since been our goal to make Flyte planning a community endeavor. Pace

7/18/2022
Flyte 1.1 Release

Platform User Improvements Support for Optional types. With the inclusion of Union types in flytekit, we can now support optional types. Flyte Deck is now available. Please take a look at the documentation and also the OSS presentation that was done a few weeks back. Backend Improvements Allow different cookie settings in Admin. Pluggable middleware in Admin authentication.

7/16/2022
Untitled

Flyte 1.0.2-b1 Platform Feature Server-side compiler should strip Type Metadata Bugfix With GRPC v1.46.0 non-ascii chars are not permitted in grpc metadata Housekeeping Configure grpc_health_prob in admin Feature In Flytectl use Launchplan with latest version for scheduled workflows Bugfix Pods started before InjectFinalizer is disabled are never deleted Housekeeping Checksum grpc_health_probe Feature Allow to choose Spot Instances at workflow start time

5/25/2022
Flyte v1.0.0

Flyte 1.0 represents the first major release of the platform. Flyte APIs, and tools can now be considered [stable]. While it's impossible to assert so, any workflow/task written against flytekit v1.0.0 should be expected to run against all v1.x.x versions. Quick Stats: Stat Change 4,125 PRs Merged

4/26/2022
Read more from Flyte
Published on HackMD