Flyte v1.0.2 Changelog
General
- Housekeeping Update single binary component in releases and bump version of contour helm chart
Platform
- Bugfix fix flyte-deps helm chart version
- Bugfix Re-order clusterresourcesync annotations in helm chart
- 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
- Feature Use the same pod annotation formatting in syncresources cronjob
- Housekeeping Migrate flyte sandbox docker image to use flyte-dep & flyte-core
- Feature Buf integration for proto release
Flyteconsole
- Refactor Move to monorepo structure to allow separate FlyteConsole into plugins system
- Feature Add support for StructuredDataSet Input/Output type
- Feature Updated Task details page to be able to browse different task versions
- Feature Updated Input/Output and TaskDetails representation - now you can collapse parts of it.
- Feature Show new map tasks in the GraphView with information of which subtasks are in which phase(running, erroring, succeeded)
- Feature Add interruptible override to launch forms
- Bugfix ensure that setups with different domains for console and admin API properly works
- Bugfix Fixes one of the crashes in Graph component for Viel All Workflow section
- Bugfix ensure that admin version is fully shown FC#465
- [Bugfix] Small cosmetic updates: flyteorg/flyteconsole#451, flyteorg/flyteconsole#386, and flyteorg/flyteconsole#398
- Feature Map Tasks - allow to check statuses of all retries per child task
- Feature Allow to rerun single task in execution page
- [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.