1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/datacatalog/commit/faa86dbf56cce108f2c0b91f8fa2a99f67c1586f|faa86dbf>

- Publish multi-architecture image (#88) flyteorg/datacatalog

Release - v1.0.41 New release published by flyte-bot Changelog • faa86db Publish multi-architecture image (#88) flyteorg/datacatalog

Release - v1.4.1 New release published by flyte-bot 1.4.1 (2023-01-09) Bug Fixes • Dependency of release pipeline (#664) (516bbff) flyteorg/flyteconsole

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytepropeller/commit/0b5007b1c7157213deff1f9a4c65bec86e9f1b63|0b5007b1>

- Publish multi-architecture image (#514) flyteorg/flytepropeller

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyteadmin/commit/cb1224b0554347e62ea99e4495d0057f885f4fff|cb1224b0>

- Publish multi-architecture image (#510) flyteorg/flyteadmin

#509 Debug multi-architecture image build Pull request opened by jeevb on <!date^1673075110^{date_short}|2023-01-07T07:05:10Z> flyteorg/flyteadmin DCO: DCO ✅ 2 other checks have passed 2/3 successful checks

#3221 Update Flyte components Pull request opened by flyte-bot Updated flyte deployment • Updated GCP Flyte kustomize generated manifest file • Updated EKS Flyte kustomize generated manifest file • Updated Sandbox Flyte kustomize generated manifest file • Updated TEST Flyte kustomize generated manifest file • Updated GCP Flyte helm generated manifest file • Updated EKS Flyte helm generated manifest file • Updated Sandbox Flyte helm generated manifest file • Updated TEST Flyte helm generated manifest file • Auto-generated by [flyte-bot] flyteorg/flyte

Release - v1.1.60 New release published by flyte-bot Changelog • 0b5007b Publish multi-architecture image (#514) flyteorg/flytepropeller

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/7b401bc20aad4b665daf466b862868c1ef27a0e9|7b401bc2>

- Update Flyte components (#3221) flyteorg/flyte

Release - Flyte v1.3.0-b9 milestone release New release published by flyte-bot v1.3.0-b9 CI changes. flyteorg/flyte

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

1 new commit pushed to

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

by katrogan

<https://github.com/flyteorg/flyteadmin/commit/d6bc85d7e8295b14d57b4a13681bbeab31dbf2e3|d6bc85d7>

- Add user name to UserInfoResponse header (#507) flyteorg/flyteadmin

#66 Build multi-arch docker images Pull request opened by prabhu43 Signed-off-by: Prabhu Jayakumar j.prabhu91@gmail.com Fixes flyteorg/flyte#2935 flyteorg/flytetools ✅ All checks have passed 2/2 successful checks

#2935 [Housekeeping] Produce multi-arch images in CI/CD pipelines Issue created by hajapy Describe the issue Update the build pipelines to also produce arm64 images. At a glance, I think these workflows would need to be updated: https://github.com/flyteorg/flytetools/blob/master/.github/workflows/docker_build.yml#L34 https://github.com/flyteorg/flytetools/blob/master/.github/workflows/publish.yml#L36 https://github.com/flyteorg/flyte/blob/master/.github/workflows/create_release.yml I would suggest to look into using the official docker actions if possible: https://github.com/docker/setup-buildx-action https://github.com/docker/build-push-action What if we do not do this? Unable to use official flyte images on arm64 instances. Users would need to build their own images of all the flyte control plane components. Related component(s) 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/flyte/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/162c8dbe28c53d8b92368f0da55a7d7e879003fb|162c8dbe>

- Add conditional around the admin secrets (#3213) flyteorg/flyte

#3141 [BUG] Don't require flyte-admin-secrets for standalone cluster resource sync Issue created by andrewwdye on <!date^1670461457^{date_short}|2022-12-08T01:04:17Z> Describe the bug 18be8cc#diff-b87b59c495047ee004f0743b6970f8bbd98c7e26cf38c9e916927eb0c4edbdd1R42 added a default mount for

flyte-admin-secrets

in support of multi-cluster resource sync. These secrets should not be required when running cluster resource sync in standalone mode. Expected behavior

flyte-admin-secrets

are not required when running cluster resource sync in standalone mode Additional context to reproduce Deploy cluster resource sync with

standaloneDeployment: true

and without secrets defined. Container will fail with

Unable to attach or mount volumes: unmounted volumes=[flyte-admin-secrets]

Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - v1.1.68 New release published by flyte-bot Changelog • cb1224b Publish multi-architecture image (#510) flyteorg/flyteadmin

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/1311ea47242e4f32a9dc0769b6a51554ab41ee80|1311ea47>

- Read structured dataset from a folder (#1406) flyteorg/flytekit

Release - v1.1.69 New release published by flyte-bot Changelog • d6bc85d Add user name to UserInfoResponse header (#507) flyteorg/flyteadmin

#515 Add TensorFlow to loader.go Pull request opened by pingsutw Signed-off-by: Kevin Su pingsutw@gmail.com TL;DR Add

TensorFlow

to loader.go, so we can load

TensorFlow

plugin while starting the propeller. 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 https://flyte-org.slack.com/archives/C045P7GBGBU/p1673314641468229 Follow-up issue NA flyteorg/flytepropeller

1 new commit pushed to

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

by samhita-alla

<https://github.com/flyteorg/flytesnacks/commit/b61d89d8e5c4b4e7ce376d3fc8f3a97e76af0cf4|b61d89d8>

- Fix walkthrough command for pima diabetes classification example (#940) flyteorg/flytesnacks

Release - flytesnacks v0.3.160 New release published by flyte-bot Changelog • b61d89d Fix walkthrough command for pima diabetes classification example (#940) flyteorg/flytesnacks

1 new commit pushed to

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

by honnix

<https://github.com/flyteorg/flytekit-java/commit/c5640872e4c605929a7163cdc611821282ab525b|c5640872>

- Update maven central URL (#163) flyteorg/flytekit-java

#3224 [UI Feature] launch LaunchPlan directly from LaunchPlan list/details Issue created by flixr Motivation: Why do you think this is important? Took us a while to find that we could launch a LaunchPlan from the UI via workflows -> launch -> select launchplan. Instead I expected to be able to launch a LaunchPlan from where it is displayed. Goal: What should the final outcome look like, ideally? Add a launch button to LauchPlans directly, making this a shortcut and more discoverable. 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/flytepropeller/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/8cbb05a0fd43feae35f3611042769c6a7b181728|8cbb05a0>

- Add TensorFlow to loader.go (#515) flyteorg/flytepropeller

Release - v1.1.61 New release published by flyte-bot Changelog • 8cbb05a Add TensorFlow to loader.go (#515) flyteorg/flytepropeller

#665 Bug: Archived launchplans are not currently being filtered in the launch plan list Issue created by jsonporter Users have requested support for archiving launch plans. Acceptance Criteria: • Users can archive LP from search UI • Archived LPs are excluded from LP search UI • Filter text is 'Include Archived' • Filter is inclusive (like task/workflow toggle implemented in 661). • Archived LP are not included in drop-down on launch form UI unless that LP is the current selected LP (eg, relaunching an execution) flyteorg/flyteconsole

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flytesnacks/commit/9e28039d4b8ddf5c5f951859740af05c4bf6e26f|9e28039d>

- Document IgnoreOutputs exception (#938) flyteorg/flytesnacks

#3225 [Core feature] Raw claims should be passed along as header metadata Issue created by katrogan Motivation: Why do you think this is important? It would be useful for the flyteadmin authorization server /me endpoint handler to return raw claims from the OIDC provider in addition to the standard user info Goal: What should the final outcome look like, ideally? Raw claims should be propagated from the flyteadmin authorization server as metadata headers Describe alternatives you've considered N/A 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