Flyte v0.19.3-b2 milestone release

0.19.3-b2 Change Log

System

• Allow clusterName to be passed to flytepropeller through the Values.yaml file.

Flyte v0.19.3-b1 milestone release

0.19.3-b1 Change Log

System

• Allow extraArgs to be passed to FlytePropeller, DataCatalog and FlyteAdmin deployments.

Flyte v0.19.2 milestone release

0.19.2 Change Log

UX

• Added support for Archive/Unarchive Workflow Executions
• Added Support for viewing node metadata on unexecuted nodes
• Minor bug fixes

FlyteKit

• Introducing the new StructuredDataset type. Turn it on by setting the env var FLYTE_SDK_USE_STRUCTURED_DATASET=TRUE. It'll be turned on by default in v1.0. Docs
• This release also removes the legacy API.

Review the full changelog here.

System

• Archive (issue).
  Expose the ability to archive/unarchive executions to remove clutter from the UI.
• Security Updates:
  • Access token validation supports multiple-audience tokens (issue)
  • flytectl supports caching access tokens for multiple endpoints at the same time (issue)
• You can use flytectl to update projects' display names and descriptions (issue)

  flytectl update project  --id data --name datadata --description "Team that manage Data Platform" --labels "team=data,managedby=flyte"

Flyte v0.19.2-b5 milestone release

0.19.2-b5 Release ChangeLog

System

1. Mount admin auth creds for cluster resource sync run in standalone mode.

Flyte v0.19.2-b4 milestone release

0.19.2-b4 Release ChangeLog

System

1. Additions to flyte-core helm chart to allow deploying cluster resource sync as a standalone process with the latest image version.

Flyte v0.19.2-b3 milestone release

0.19.2-b3 Release ChangeLog

System

1. Update flyte-core helm chart to allow deploying cluster resource sync as a standalone process.

Flyte v0.19.2-b1 milestone release

Flyte v0.19.2-b1

Resolving the minio port conflict.

Flyte v0.19.1 milestone release

0.19.1 Release ChangeLog

FlyteKit

No new flytekit releases as part of this release

UX

1. Rendering of a new 'terminating' phase while an aborted execution is processed
2. Misc. bug fixes

System

1. Upgrading flyteadmin migrate due to an issue in gorm's postgres driver. This release fixes the migration path to update id column database types.

Documentation

1. Updated docsearch version
2. Refreshed ToC cards

Flyte v0.19.0 milestone release

0.19.0 - Eagle Release ChangeLog

v0.19.0 codenamed Eagle, for Flyte marks the first quarterly release for Flyte in 2022. To remind, starting October 2021, the Flyte community has decided to use patch version for monthly releases and minor versions for Quarterly releases.

The release is the last in set of the 3 releases. The prior 2 can be found at

• v0.18.1 changelog
• v0.18.2 changelog

The focus on this release and the previous 2 can be divided into 2 parts

• UX (UI and Flytekit)
• System

As part of the UX, we have been focusing a lot on getting feature breadth in the UI for Flyte (flyteconsole). This is following our current UX design philosophy. We plan to complete the full design in the next 3 months and then create a fully re-designed UX (Stay tuned for more on this.)

The design for Flytekit has been wildly appreciated and we have been heavily working on improving it further and allowing users to express their various requirements much more easily. We are pretty certain on the design of flytekit and we promise that all our users will not experience a breaking change when we release a v1.0.0.

The focus on the system always is improving reliability and performance. This quarter we were able to drastically improve the size of workflows that can be executed and improvements in transition performance between nodes.

The Eagle release sets a great stage for v1.0.0 - Phoenix release slated for April 2022. We think, the Phoenix release will be a major milestone for the platform and we will be focusing on UX improvements.

Updates specific to v0.19.0

Closed Issues

UX

• New search UX for workflows
• Support for "security context" in launch workflow form
• Support for Google Analytics
• Minor fixes:
  • Removed DISABLE_AUTH env var
  • Issue with launch plan metadata not showing on execution view

FlyteKit

Please find the full changelog here.

Changes

• Support for delayed annotations by @bethebunny in flyteorg/flytekit#760
  Users can now add from __future__ import annotations to the top of their code to stop using "" in type hints.
• Add cache_serialize parameter to tasks by @hamersaw in flyteorg/flytekit#673
  Turn this on to avoid two cached tasks from running at the same time. Make sure you're at least at propeller v0.16.1 or later and 0.3.17 or later in datacatalog.
• Use functools.wraps basically within the task and workflow decorators, @bstadlbauer in flyteorg/flytekit#780

System

• Auto-horizontal-scale for FlytePropeller Docs
• flytectl sandbox start will add sandbox cluster context to the local kubeconfig. No more fiddling with env vars to get your KUBECONFIG right!
• Egress Events Docs
• Full reference of Admin and Propeller configs.

Flyte v0.18.2 milestone release

0.18.2 Release ChangeLog

Closed Issues

UX

• Added advanced options to launch form
• Added support for all tasks-types (task execution view)
• Replaced execution id's with node id's on execution list-view
• Fixed bug with some properties not being repopulated on relaunch
• minor fixes

FlyteKit

See the flytekit 0.25.0 release notes for the full list of changes. Here are some of the highlights:

• Improved support for tasks that run shell scripts
• Support for more types in dataclasses:
  • enums
  • FlyteFile and FlyteSchema
• flyteremote improvements, including:
  • Access to raw inputs and outputs
  • Ability to serialize tasks containing arbitrary images
  • Improved UX for navigation of subworkflows and launchplans
  • Support for FlytePickle

System

• Various stability fixes.

• New docker image tags!

  In addition to component-specific versions released from each of the flyte repositories (e.g. flytepropeller:v0.16.5), new images will be re-tagged and pushed that match the flyte release version (e.g. the upcoming flytepropeller-release:v0.18.2). This makes it easier to make sure all your deployments are on the same version to ensure best compatibility.

• Helm changes

  • flyte-core helm chart has reached release preview and can be leveraged to install your cloud(AWS/GCP) deployments of flyte.
  • Going forward flyte-core will install flyte native scheduler, For AWS backword compatibility you need to define workflow_schedule.type to aws. (#1896)
  • flyte helm chart has been refactored to depend on flyte-core helm chart and install additional dependencies to continue to provide a sandboxed installation of flyte.

  Migration Notes

  As part of this move, flyte helm chart is becoming the canonical sandbox cluster. It comes with all external resources needed to fully standup a Flyte cluster. If you have previously been using this chart to deploy flyte on your cloud providers, there will be changes you need to do to migrate:

  • If you have your own myvalues.yaml, you will need to add another nesting level under flyte: for the sections that are now managed through flyte-core. For example:

    configmaps:
      ...
    flyteadmin:
      ...
    minio:
      ...
    countour:
      ...

    to:

    flyte:
      configmaps:
        ...
      flyteadmin:
        ...
    minio:
      ...
    countour:
      ...    

  • Alternatively, if you do not have any dependency on external flyte depdencies, you can keep your myvalues.yaml and switch to using flyte-core helm chart directly with no changes.