# 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 | | 18,983 | Comments Added | | 1,511 | Issues Created | ## ChangeLog ### FlyteKit * File ignore in fast register Many thanks to @bimtauer for adding this much requested feature! When packaging local files for fast-registration, flytekit will now respect `.gitignore` and `.dockerignore`. Please see the [PR](https://github.com/flyteorg/flytekit/pull/967) for more information. * `pyflyte run` The pyflyte run command has been slightly updated to not need a `:` when selecting the workflow. ```bash $ pyflyte run --remote example.py wf --n 500 --mean 42 --sigma 2 ``` * Script mode: register and run workflows all in one command using a pre-defined base image * Flyte remote GA: register workflows and interact with Flyte execution artifacts programmmatically * Configuration overhaul: use the same config across flytekit and flytectl * Fast register without having AWS/GCP or other cloud credentials on your laptop, all you need is Flyte access ### Core Platform * Improved Garbage Collector Garbage collection logic has been revamped to reduce load on KubeAPI and ensure terminated workflows are cleaned up in a timely fashion. **[Action Required]** Due to the change in the computation of how to clean up terminated workflows, users are advised to clean up old workflows once by running the following command per namespace: ```bash kubectl delete fly -l termination-status=terminated --all-namespaces --cascade='background' --wait=false --force --grace-period=0 ``` * Single binary: deploy the entire Flyte back-end as a single binary. This speeds up sandbox and improves the local contributor experience. Coming soon: faster deployment for small-scale use-cases * Improved map task subtask handling - Cache status reporting - Individual log links mapped to subtasks - Interruptible failure handling for spot instances - Secret injection * Improved performance for fetching and rendering dynamic nodes * Set raw output data config at create execution time * Execution overrides at the project level for - Kubernetes service account - AssumableIAMRole - OutputLocationPrefix ### Console * Project dashboard page with recent executions overview along with a config and other settings summary * Dynamic workflow rendering * Map task UI and UX improvements: see logs, retry attempts and more at the subtask level
Last changed by  
 
Flyte
Open Source Flyte Team Notes
60

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
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,

7/5/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
Read more from Flyte
Published on HackMD