Skip to content

Releases: flyteorg/flyte

Flyte v1.1.0-b1 milestone release

30 Jun 23:23
d60da16
Compare
Choose a tag to compare
Pre-release

Flyte v1.1.0-b1 Changelog

will be filled in later

Flyte v1.0.2 milestone release

07 Jun 20:53
106a814
Compare
Choose a tag to compare

Flyte v1.0.2 Changelog

General

  1. Housekeeping Update single binary component in releases and bump version of contour helm chart

Platform

  1. Bugfix fix flyte-deps helm chart version
  2. Bugfix Re-order clusterresourcesync annotations in helm chart
  3. Feature Server-side compiler should strip Type Metadata
  4. Bugfix With GRPC v1.46.0 non-ascii chars are not permitted in grpc metadata
  5. Housekeeping Configure grpc_health_prob in admin
  6. Feature In Flytectl use Launchplan with latest version for scheduled workflows
  7. Bugfix Pods started before InjectFinalizer is disabled are never deleted
  8. Housekeeping Checksum grpc_health_probe
  9. Feature Allow to choose Spot Instances at workflow start time
  10. Feature Use the same pod annotation formatting in syncresources cronjob
  11. Housekeeping Migrate flyte sandbox docker image to use flyte-dep & flyte-core
  12. Feature Buf integration for proto release

Flyteconsole

  1. Refactor Move to monorepo structure to allow separate FlyteConsole into plugins system
  2. Feature Add support for StructuredDataSet Input/Output type
  3. Feature Updated Task details page to be able to browse different task versions
  4. Feature Updated Input/Output and TaskDetails representation - now you can collapse parts of it.
  5. Feature Show new map tasks in the GraphView with information of which subtasks are in which phase(running, erroring, succeeded)
  6. Feature Add interruptible override to launch forms
  7. Bugfix ensure that setups with different domains for console and admin API properly works
  8. Bugfix Fixes one of the crashes in Graph component for Viel All Workflow section
  9. Bugfix ensure that admin version is fully shown FC#465
  10. [Bugfix] Small cosmetic updates: flyteorg/flyteconsole#451, https://github.com/flyteorg/flyteconsole/issues/386, and https://github.com/flyteorg/flyteconsole/issues/398
  11. Feature Map Tasks - allow to check statuses of all retries per child task
  12. Feature Allow to rerun single task in execution page
  13. [Plugins]: Adds flyte-api plugin package. You can check basic how to info and consume package from https://www.npmjs.com/package/@flyteconsole/flyte-api . It will allow you to authorize you flytectl queries and perform api requests from your app. At this point only request without included data in body is allowed. More work is planned in future updates.

Flytekit

  1. Feature pyflyte run should support executing tasks
  2. Bugfix Dot separated python packages does not work for pyflyte
  3. Bugfix Pyflyte run doesn't respect the --config flag
  4. Bugfix Read packages from environment variables

Flyte v1.0.2-b2 milestone release

26 May 02:30
e0a500a
Compare
Choose a tag to compare
Pre-release

Flyte 1.0.2-b2

Platform

  • Bugfix fix flyte-deps helm chart version
  • Bugfix Re-order clusterresourcesync annotations in helm chart

Flyte v1.0.2-b1 milestone release

25 May 08:25
4386d2a
Compare
Choose a tag to compare
Pre-release

Flyte v1.0.2-b1 Changelog

Platform

  1. Feature Server-side compiler should strip Type Metadata
  2. Bugfix With GRPC v1.46.0 non-ascii chars are not permitted in grpc metadata
  3. Housekeeping Configure grpc_health_prob in admin
  4. Feature In Flytectl use Launchplan with latest version for scheduled workflows
  5. Bugfix Pods started before InjectFinalizer is disabled are never deleted
  6. Housekeeping Checksum grpc_health_probe
  7. Feature Allow to choose Spot Instances at workflow start time
  8. Feature Use the same pod annotation formatting in syncresources cronjob

Flytekit

  1. Feature pyflyte run should support executing tasks
  2. Bugfix Dot separated python packages does not work for pyflyte
  3. Bugfix Pyflyte run doesn't respect the --config flag
  4. Bugfix Read packages from environment variables

Flyte v1.0.1 milestone release

06 May 00:27
5570eff
Compare
Choose a tag to compare

v1.0.1 Release ChangeLog

System

  1. Bugfix Addresses the regression to allow empty default complex values for workflow parameters
  2. Bugfix for flyteadmin not respecting fallback substitution for execution spec parameters (e.g. labels, annotations, security context, raw output data config)
  3. Bugfix Bump stow version to fix issue with GoogleAccessId

Flytekit

  1. Bugfix Task chaining without the use of the create_node utility function
  2. Bugfix Improved validation of image config objects

Flyte v1.0.0 milestone release

26 Apr 12:02
81044f8
Compare
Choose a tag to compare

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 for more information.
  • pyflyte run
    The pyflyte run command has been slightly updated to not need a : when selecting the workflow.
    $ 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:
    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

Flyte v1.0.0-b1 milestone release

21 Apr 17:37
289e6db
Compare
Choose a tag to compare
Pre-release

Flyte v1.0.0-b1 Changelog

Flyte v0.19.4 milestone release

15 Apr 18:19
52fc1df
Compare
Choose a tag to compare

Flyte v0.19.4 Changelog

Core Platform

  • 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

SDK

  • 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 or other cloud credentials on your laptop, all you need is Flyte access

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

Flyte v0.19.3 milestone release

10 Mar 20:23
2ece384
Compare
Choose a tag to compare

Flyte v0.19.3 Changelog

Updates

Core Platform

  • Support for Type Annotations complete.
  • BigQuery plugin
  • Support for hash-based caching of schema and structured dataset offloaded types.
  • Configurable gRPC message size.
  • Cleanup of database connection handling in Admin.
  • Bug and performance fixes around

SDK

  • New current_task_metadata field in StructuredDatasetDecoder interface.
  • Authentication configs removed (auto-detected from Admin)
  • AWS Batch Task
  • Callable fetched entities

See the complete notes for flytekit v0.31.0. Keep in mind we'll be releasing v0.32.0 in a couple days. At that time the StructuredDataset type will be the default Flyte type for dataframes!

UI

  • Fix node IDs for certain nested scenarios where node IDs are shared across nested workflows.

Component Versions

Admin v0.6.92 to v0.6.112
Propeller v0.16.19 to v0.16.32
Console v0.41.0 to v0.43.0

Flyte v0.19.3-b3 milestone release

18 Feb 21:56
230ad92
Compare
Choose a tag to compare
Pre-release

0.19.3-b3 Change Log

System

  • Properly control Athena token length in plugin
  • Relaxed StructuredDataset column compatibility