Release - v1.1.93 New release published by flyte-bot Changelog • 507ad44 Added start time for supporting restarts for fixed rate schedules (#476) flyteorg/flyteadmin

#1624 update GH workflow for external plugin service Pull request opened by pingsutw TL;DR update GH workflow for external plugin service Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue NA Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/e44b8027bd0f59c0f90eb5f86bfa181aebad0d74|e44b8027>

- update GH workflow for external plugin service (#1624) flyteorg/flytekit

Release - Build external plugin service image New release published by pingsutw flyteorg/flytekit

#3651 [Plugin] Remove print in SQLAlchemyTaskExecutor Issue created by sofianelounici Problem When using a SQLAlchemyTask, there are two prints which are annoying (especially when running multiple queries and we want light logging): https://github.com/flyteorg/flytekit/blob/db7d1eb480cea24504d94419981859bfc9ef6c62/plugins/flytekit-sqlalchemy/flytekitplugins/sqlalchemy/task.py#L129 https://github.com/flyteorg/flytekit/blob/db7d1eb480cea24504d94419981859bfc9ef6c62/plugins/flytekit-sqlalchemy/flytekitplugins/sqlalchemy/task.py#L132 Solution Possibility to remove them ? Are they useful ? flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/941fa412ae24ec05fcf8d132dce360be6db150f6|941fa412>

- Update Flyte components (#3650) flyteorg/flyte

Release - Flyte v1.6.0-b1 milestone release New release published by flyte-bot Flyte v1.6.0-b1 What's Changed Console • feat: show launchplan in execution table by @pradithya in flyteorg/flyteconsole#738 • feat: show launch plan information in workflow's schedules by @pradithya in flyteorg/flyteconsole#739 • fix: passthrough runtime env vars by @ursucarina in flyteorg/flyteconsole#741 • chore: add fallback to task execution link by @ursucarina in flyteorg/flyteconsole#743 • chore: allow custom subnav by @ursucarina in flyteorg/flyteconsole#734 • fix: force node executions to pull their status by @ursucarina in flyteorg/flyteconsole#737 • chore: fix details panel card padding by @ursucarina in flyteorg/flyteconsole#745 • chore: fix crash by @ursucarina in flyteorg/flyteconsole#746 • [UI Feature] Add full-list log output to execution detail panel by @james-union in flyteorg/flyteconsole#744 • TLM add log-message window to left panel by @james-union in flyteorg/flyteconsole#748 • [Snyk] Upgrade eslint from 8.31.0 to 8.33.0 by @EngHabu in flyteorg/flyteconsole#695 • chore: [tlm] comprehensive node execution query by @ursucarina in flyteorg/flyteconsole#749 • chore: guard against /tasks failing by @ursucarina in flyteorg/flyteconsole#750 • chore: propagate dynamic parent id by @ursucarina in flyteorg/flyteconsole#751 • Add support fetching description entity by @pingsutw in flyteorg/flyteconsole#735 Admin • Infer GOOS and GOARCH from environment by @jeevb in flyteorg/flyteadmin#550 • Enrich TerminateExecution error to tell propeller the execution already terminated by @EngHabu in flyteorg/flyteadmin#551 • Address resolution by @wild-endeavor in flyteorg/flyteadmin#546 • Add migration to turn

parent_id

column into

bigint

only if necessary by @eapolinario in flyteorg/flyteadmin#554 Propeller • Moved controller-runtime start out of webhook Run function by @hamersaw in flyteorg/flytepropeller#546 • Fixing recovering of SKIPPED nodes by @hamersaw in flyteorg/flytepropeller#551 • Remove resource injection on the node for container task by @ByronHsu in flyteorg/flytepropeller#544 • Infer GOOS and GOARCH from environment by @jeevb in flyteorg/flytepropeller#552 • fix makefile to read variables from environment and overrides by @jeevb in flyteorg/flytepropeller#554 • Remove BarrierTick by @hamersaw in flyteorg/flytepropeller#545 • Check for TerminateExecution error and eat Precondition status by @EngHabu in flyteorg/flytepropeller#553 • Setting primaryContainerName by default on Pod plugin by @hamersaw in flyteorg/flytepropeller#555 • Implement ability to specify additional/override annotations when using Vault Secret Manager by @pradithya in flyteorg/flytepropeller#556 • Maintaining Interruptible and OverwriteCache for reference launchplans by @hamersaw in flyteorg/flytepropeller#557 • Added support for aborting task nodes reported as failures by @hamersaw in flyteorg/flytepropeller#541 • Added support for EnvironmentVariables on ExecutionConfig by @hamersaw in flyteorg/flytepropeller#558 • Fast fail if task resource requests exceed k8s resource limits by @hamersaw in flyteorg/flytepropeller#488 • @ByronHsu made their first contribution in flyteorg/flytepropeller#544 flyteorg/flyte

Deployment to github-pages by flyte-bot flyteorg/flyte

#348 Allow 0 worker in pytorch plugins & Add objectMeta to PyTorchJob Pull request opened by ByronHsu TL;DR 1. Kubeflow PyTorch can be configured to use 0 workers when running distributed PyTorch jobs. In this case, the training job would run on a single machine (the master node), without any additional worker nodes. 2. Pass objectMeta to PyTorchJob Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue flyteorg/flyteplugins ✅ All checks have passed 6/6 successful checks

#349 Enable pod template and Use copy to construct head/worker in ray plugin Pull request opened by ByronHsu Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Why? 1. The current implementation is unable to parse podtemplate 2. The current implementation will lose container information (like

Volume

) when constructing worker/head pod because it created a new container from scratch What? 1. Use

flytek8s.ToK8sPodSpec

to parse both container and pod type 2. Copy the container from the original primary container instead of creating a new one flyteorg/flyteplugins ✅ All checks have passed 6/6 successful checks

#1625 Beautify deviceflow prompt Pull request opened by ByronHsu Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Complete description To make deviceflow prompt more prominent Note: for why

verification_url_completed

is removed, check #1611 flyteorg/flytekit Codecov: 71.01% (-0.03%) compared to c65397d Codecov: 66.66% of diff hit (target 71.04%) ✅ 28 other checks have passed 28/30 successful checks

#3654 refactor: Values.configuration.flyte-binary -> Values.flyte-core-components Pull request opened by ossareh an example of what the nesting change suggested here: #3631 (comment) would look like flyteorg/flyte DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#1626 Add support for using union type in subworkflow's input Pull request opened by pingsutw TL;DR merge into #1605 flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-envd) GitHub Actions: build-plugins (3.8, flytekit-duckdb) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: lint GitHub Actions: build (windows-latest, 3.11) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: docs ✅ 2 other checks have passed 2/26 successful checks

#74 Fix push image conditional Pull request opened by wild-endeavor flyteorg/flytetools ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytetools/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flytetools/commit/4e5c5c0e04d9c21292daf213bce7a83184fe700e|4e5c5c0e>

- Fix push image conditional (#74) flyteorg/flytetools

#3656 when defining a reference_task, allow omitting version to refer to the latest deployed version of the task Issue created by ophiry Motivation: Why do you think this is important? reference tasks are useful to allow a client call a server task with low coupling ("batch service") the need to specify explicit version breaks this decoupling (the client needs to be updated on any new server version) Goal: What should the final outcome look like, ideally? keep the same API, but make the version field optional. if the field is missing, lookup the latest version of the task (preferably at runtime, not deploy time) Describe alternatives you've considered I tried to lookup the task version using remote.fetch_task but this will run at deploy time (so the client will be coupled to the version present when it was deployed) also, this adds boilerplate to the code Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyteidl/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flyteidl/commit/44ae4010d76267dfa2fbcd42148781be067ed3bb|44ae4010>

- Add envs to execution spec (#400) flyteorg/flyteidl

#1627 Change flytekit Pytorch, TFJob and MPI plugins to use new kubeflow config Pull request opened by yubofredwang TL;DR We have updated the plugin config in flyteidl and flytepropeller. This PR updates flytekit to uses the new configs for kubeflow plugins including: pytorch, tfjob and mpijob. Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description This change is backward compatible. If users continue using the old config like

@task(
task_config=TFJob(num_workers=1)
)
def my_task:
      ...

This still works. However, the new config should look like:

@task(
task_config=TFJob(worker=Worker(replicas=1))
)
def my_task:
      ...

Tracking Issue flyteorg/flyte#3308 flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#3657 Adding nodeselector to flyte-binary chart and values Pull request opened by itsyitsy Describe your changes Added nodeselector field to flyte-binary helm chart. Added example and field to values.yaml. Reference what node-selector can be used for: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte GitHub Actions: sandbox-bundled-functional-tests GitHub Actions: build-and-push-sandbox-bundled-image GitHub Actions: build-and-push-single-binary-image GitHub Actions: generate_helm ✅ 8 other checks have passed 8/12 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteplugins/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flyteplugins/commit/9a2bbbaf2f3ac9e38222ba7755ac4bda1ac2fdb7|9a2bbbaf>

- Change kubeflow plugins to allow settings specs for different replica (#345) flyteorg/flyteplugins

Release - v1.0.58 New release published by flyte-bot Changelog • 9a2bbba Change kubeflow plugins to allow settings specs for different replica (#345) flyteorg/flyteplugins

Release - v1.5.3 New release published by flyte-bot Changelog • 44ae401 Add envs to execution spec (#400) flyteorg/flyteidl

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flyte/commit/fd22cb52f560f78180de58a89ba27f0a02ce0c35|fd22cb52>

- Remove mentions to DISABLE_AUTH (#3649) flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyteidl/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flyteidl/commit/9247ff0474e9bee94a1ef47a0ab228044816e536|9247ff04>

- Support union and none type in flyteidl (#401) flyteorg/flyteidl

#3094 [BUG] Support union and structured data set types in flytectl Issue created by pmahindrakar-oss Describe the bug Currently flytectl doesn't support creating /extracting union types and hence is not able to creation executions for tasks which utilize these types. Add support for these in the following files and consume the updated idl in flytectl https://github.com/flyteorg/flyteidl/blob/master/clients/go/coreutils/literals.go https://github.com/flyteorg/flyteidl/blob/master/clients/go/coreutils/extract_literal.go And test it by creating an execution which involves these types from flytectl Expected behavior flytectl should be able to launch executions involving tasks with union and structured data set Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#558 manually push 1.1.92 Pull request opened by wild-endeavor on <!date^1683668086^{date_short}|2023-05-09T21:34:46Z> Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version Codecov: 58.39% (-0.25%) compared to 00915ec ✅ 10 other checks have passed 10/14 successful checks

Release - v1.5.4 New release published by flyte-bot Changelog • 9247ff0 Support union and none type in flyteidl (#401) flyteorg/flyteidl

#559 V1.1.92 push Pull request opened by wild-endeavor on <!date^1683671471^{date_short}|2023-05-09T22:31:11Z> Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Bump Version Codecov: 58.39% (-0.25%) compared to 00915ec ✅ 11 other checks have passed 11/14 successful checks

#559 always push Pull request opened by wild-endeavor Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytepropeller ✅ All checks have passed 1/1 successful checks

#3658 [Core feature] flytekit should compile and register tasks within dynamic Issue created by Nan2018 Motivation: Why do you think this is important? When using

FlyteRemote.register_workflow

the tasks within the workflow are also registered. However, if there is a dynamic task which contains other tasks/workflows, those tasks/workflows are not registered. Goal: What should the final outcome look like, ideally?

FlyteRemote.register_workflow

should register all tasks/workflows including ones inside dynamic. Describe alternatives you've considered currently the workaround is to manually register the task / workflow in the dynamic Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte