🎉 flytekit + flyte 1.14 are here The biggest releases of the year in terms of # features and new contributors. Highlights: • Dataclasses, dicts, and Pydantic BaseModels are finally supported on their native formats. • Consume Flyte from Notebooks natively, no plugins required. • `FlyteDirectory`is now supported as input to

ContainerTask

• No more hitting gRPC limits when moving large data, this is now offloaded automatically. • Much more! Dive into the flyte and flytekit release notes (which we are trying to make more descriptive than before 🙂 ). This truly feels like a team effort with the 30+ developers who merged their first contribution to Flyte. 💜Thank you!💜

📣 Monthly Contributors Spotlight Here’s a roundup of the contributions from our community members this month: • @microscopic-oyster-89823 updated the single binary YAML configuration. • @cool-lifeguard-49380 implemented fixes for distributed error aggregation opt-in and made appprotocols optional in the helm chart. • @clean-glass-36808 introduced refresh token support for device flow authentication. • @witty-action-93503 contributed a jupyter notebook example to flyte docs. • @echoing-account-76888 added raw container docs and examples using imagespec in container task. • @nutritious-telephone-58961 updated the JSON schema version priority and added more dataclass tests. • Vincent customized the demo cluster port. A huge shoutout to @creamy-shampoo-53278, @ancient-lawyer-94886, @dry-parrot-15675, and @full-toddler-99513 for your continued support and contributions—you make Flyte better every day! Thank you all for your incredible work! 🙌

🌏 Hello everyone! 🔎 Union is conducting research to understand the work experiences, challenges, and needs of ML/AI Managers to better support your workflows. Looking for: 🤝🏽 ML/AI Managers & analogous roles kubernetes Must be using Kubernetes 🤖 Must be fine-tuning LLMs Discussions are informal, 60 min or less, & no prep is needed! Your time and thoughts are valuable! 💰 Participants will receive a $60 Visa Gift Card If this sounds like you, grab a time slot here: https://calendly.com/chelsea-union/ml-r3 Questions? Contact chelsea@union.ai

Join the upcoming community sync to learn how the most recent major Flyte release enables higher flexibility and robustness for AI workflows: https://www.linkedin.com/events/fromnotebookstoproductionwithfl7283168164148875264/theater/ Tuesday, Jan. 21 9:00 am PT We hope to see you there 😀

📓 Support for Notebooks in Flyte and Union This week we blogged about this recent integration. It really felt like only scratching the surface on the possibilities 😎 BTW thanks again @witty-action-93503 for your invaluable contributions! ➡️ Read the blog ▶️ Join us next week for the community sync to watch a live demo and get your questions answered!

📢 In 90 minutes we'll go live with the Community Sync special episode You won't want to miss some of Flyte's core maintainers live demoing the newest features plus a preview of what's coming in 1.15 🔥 Bring your questions! Join us on LinkedIn or YouTube Today, 9:00 a.m. PT

📣 Monthly Contributors Spotlight Here’s a roundup of the contributions from our community members this month: • @creamy-shampoo-53278 enabled opening a `FlyteFile` from a remote path and added support for accessing `StructuredDataset` attributes in a dataclass. • @clean-glass-36808 cleaned up auto-refresh, added an option to disable synchronization on creation for the auto-refresh cache, and configured the Ray pod runtime class based on custom pod specs. • @dry-pizza-97077 worked on switching to domain-qualified finalizers. • @billowy-church-83438 added documentation for the Flyte K8s service agent and introduced a new Flyte agent to create, update, and delete K8s StatefulSets and services for GNN use cases. A huge shoutout to Chung Chuan Wu, @ripe-smartphone-56353, @cool-lifeguard-49380, Marcin Zabłocki, @witty-action-93503, Pranshu, and @nutritious-telephone-58961 for your continued support and contributions—you make Flyte better every day! Thank you all for your incredible work! 🙌

Hey everyone! Some recent updates: • 💪🏽The fantastic team at Adarga.ai, who gave a last year, open sourced a K8s operator that registers workflows using a CRD. Kudos! • 🎁 ICYMI: we had some of the Flyte maintainers "unboxing" the 1.14 release. • 🦜 Flyte School is so back ◦ Flyte auth deep dive + RBAC and compliance in Union ▪︎ Wed, Feb 26. 9:00 am PT ▪︎ Register ◦ Batch serving with the

flytekit-inference

plugin ▪︎ Wed, March 12. 9:00 am PT ▪︎ Register ◦ We have some topics in the queue so please vote: ▪︎ 1️⃣ Troubleshooting wf executions with Grafana/Union observability ▪︎ 2️⃣ Measuring and optimizing execution performance ▪︎ 3️⃣ Parallel computing series • Ray • Spark • MapTasks ▪︎ 4️⃣ Flyte Agents deep dive and how to build one from scratch ▪︎ Propose a topic 🙂 --- Thank you!

🦜 Flyte 1.15 is out! Here are the major highlights: 📊 Streaming Decks: Now you can see your task metrics, data, and logs in real-time while tasks are running - perfect for monitoring hyperparameter optimization and debugging! 🔐 Better Secrets Handling: Simplified secret configuration for both environment variables and files - way less verbose than before. ⚡️ Enhanced Task Caching: Unified caching system with new features like cache policies, custom salts, and the ability to ignore specific inputs from cache keys. 📦 Quality of Life Updates: - Progress bars for package creation/upload - Faster GitIgnore checks - Support for debugging @dynamic tasks - Flexible pod template overrides Check out full release notes: https://github.com/flyteorg/flyte/releases/tag/v1.15.0 💜 Thanks to 12 new contributors who made it possible!

Hello everyone: Circulating here a couple of new RFCs that are open for feedback. As a reminder, RFCs are a mechanism to discuss and design significant changes to the Flyte API, and your feedback is important; • Simplify the `Resources` API • Decentralize Flyte Agents config management Thank you!

Hi everyone: This Slack workspace has been renamed to *“Building AI Together by Union.ai*" Here’s what this means for you: Why the change? 1️⃣ Unifying Our Communities • Union.ai supports multiple open-source projects and tools—including Flyte, Pandera, and Union’s Serverless platform—and we want this workspace to be a hub for all these communities. • Whether you’re a Flyte user, a Pandera contributor, or exploring Serverless, this is your space to connect and grow. 2️⃣ Expanding Collaboration for MLOps Practitioners • While Flyte remains a core focus, we’re broadening the scope to encourage sharing best practices, lessons learned, and resources across the entire MLOps lifecycle. • Expect discussions on everything from workflow orchestration and data validation to scalable infrastructure and team workflows. Our Commitment to You ✨ What’s Not Changing: • Our dedication to helping ML and Data teams productionize AI applications remains unwavering. • Flyte-specific channels and community support will continue as always, alongside new opportunities to engage with other Union.ai projects. 🌱 What’s Growing: • More cross-community events, and collaborative problem-solving. • A stronger emphasis on real-world use cases and collective learning. Have questions or ideas? Drop them in this discussion or DM us anytime! Thank you!

📣 Monthly Contributors Spotlight Here's a roundup of this month's amazing contributors and their contributions: • @faint-pilot-24699 upgraded flyteadmin to use Mockery v2 and improved error handling by passing error messages to the failure node. • Hsuan-Chen Chen introduced support for overriding pod templates with `with_overrides`. • @clean-glass-36808 added support for merging ray head and worker node pod templates and enabled Ray pod runtime class configuration based on custom pod specs. • @echoing-account-76888 added pod template support for driver and executor pods and worked on multiple fixes in flytekit. A huge shoutout to @microscopic-truck-17789, @cool-lifeguard-49380, @big-memory-81882, @creamy-shampoo-53278, Mark Zhao, @silly-book-73230, redartera, @microscopic-oyster-89823, @average-twilight-23656, and @nutritious-telephone-58961 for your continued support and contributions—you make Flyte better every day! Thank you all for your incredible work! 🙌

Hi everyone: Union will be at the NVIDIA GTC conference next week and we'd like to connect with you: 1. Drop by the Union booth (#2022), get some swag and talk to @powerful-horse-58724 and others! 2. If you want a closer/wider discussion, you can book time with us using this link 3. Stop by the WandB booth for a live demo and see how Union and W&B empower you to iterate faster and productionize with confidence. 🗓️ Wed March 19 at 2PM For those attending, we hope to meet you there! For the rest of us I can only say: next week will be big 🚀

x-posting 😎: https://flyte-org.slack.com/archives/C06B389BX43/p1742313994282049

👋🏽 你好 Flyte community! Some recent updates: • ⚠️ To prevent a cognitive name collision with LLM Agents, Flyte Agents are being renamed to Connectors. This is a WIP and no user-level changes are expected. We'll keep you posted. • 🚀 flytekit 1.15.3 released, including: ◦ Webhook Connector: easily send workflow notifications using webhooks. No more email queues! #3058 ◦ Simplified interface for declaring Resources, including support for tuple/list and stricter validations. #3177 ◦ Customize the Spark Driver and/or Executor Pod specs using PodTemplates! #3016 ◦ Both the FileSensor and BaseSensor now support timeout, preventing the Connector from waiting indefinitely for a condition to be met. #2745 • 🔥 Great community content ◦ Datology.ai on how they achieve image-text data curation at massive scale with Flyte --> Read the blog ◦ Artera.ai on how they achieve data locality with globally distributed serving using Union! --> Read the blog • 🎤 Upcoming events ◦ ⚙️ Compound AI systems: unboxing a reference architecture ▪︎ April 3, 10:00 am PT ▪︎ Register ◦ 🌏 Build large-scale Xarray datasets for geospatial computing with Union ▪︎ April 8, 9:00am PT ▪︎ Register --- Thank you!

📣 Flyte Monthly Contributors Spotlight Here's a roundup of this month's amazing contributors and their contributions: • @creamy-shampoo-53278 contributed a long-awaited ✨ Slurm agent ✨! More details coming soon! 🎉 • @cool-lifeguard-49380 made multiple PRs updating the Kubeflow training operator and also contributed to the docs. • @early-bird-77878 added support for per-launch plan notification templates. • @bored-beard-89967 built a GeoPandas plugin and will soon share insights on scaling Xarray datasets with Flyte/Union. Stay tuned for his talk! • @echoing-account-76888 introduced support for configuring driver and executor pods in the Spark plugin. A huge shoutout to @microscopic-minister-38807, @future-football-28532, @microscopic-oyster-89823, @polite-london-84566, Daniel Brunkow, @steep-jackal-21573, @clean-glass-36808, and @average-twilight-23656 for your continued support and contributions—you make Flyte better every day! Thank you all for your incredible work! 🙌

Hello everyone: We just went live with the Flyte docs integrated into a single site. • You can access the Flyte version of the docs with the drop down selector at the top of the page • We are be rolling out redirects from the old docs to the new to reduce the number of broken links out in the wild • All old docs content should be present in the new docs. In some cases outdated or redundant content has been reorganized and rewritten but the information should still be there. • The new single-site will enable the docs to be improved and kept up to date much more effectively than was possible before • The community will still be able to contribute. We will be opening up the docs repo soon There will be some rough edges so please use this thread to report anything you may find. Thank you for your patience 🙂

Many of you folks probably do not know me - my name is Ketan Umare, and I am the original author of Flyte. Since open sourcing flyte, I have been part of this community and I am grateful to all the amazing folks who have help make Flyte an indespensible part of their Platforms. Today Flyte is used by some of the largest companies in the world to build and deliver their compound AI products. Recently, we decided to make a change, move Flyte docs to the same platform where we host union docs. Below is my rationale, Flyte is, and will always remain, an open-source project under the Apache 2.0 license and a Linux Foundation product. Our commitment to openness and independence remains unchanged. However, maintaining separate documentation sites has become an increasing burden on our small team at Union.ai. Today, Flyte’s documentation is primarily maintained by our team, rather than through broad community contributions. Managing the infrastructure for docs, in addition to maintaining Flyte itself, introduces unnecessary overhead. (Flyte docs are not simply python docs, there are golang, protobuf, python, java, terraform etc) To improve efficiency and focus on making Flyte better, we are moving our documentation to a unified platform at union.ai/docs. This decision is driven by practicality, not commercialization. Why the Move? • We are adopting Hugo, which offers *faster builds, versioning support, and local development capabilities*—major improvements over using pure Sphinx. • Hosting Flyte docs alongside Union docs reduces maintenance costs and simplifies infrastructure. • This transition allows us to improve documentation quality with more frequent updates and enhancements. We’re excited about the improvements this will bring, and you can expect to see major upgrades soon! 🚀 Let us know if you have any questions. Thanks for being part of the Flyte community!

📣 📚 Documentation Initiative Update As we wind down the week I want to take a minute and give an update on our documentation efforts. First, I want to extend a big thank you! for all the community members that helped us improve the navigation and discoverability of the content. Your reports helped us hone in on the most painful areas quickly and rapidly iterate to address them. We learned a lot this week and will put that back into practices to improve the content and UX going forward. We did improve the new site experience in various ways: 1. ✅ Content: Added, reviewed, and updated content for correctness to latest Flyte version 2. 🕵️‍♂️ Links: We poured over thousands of links and most (all?) saved bookmarks should work correctly. 3. 🕵️‍♂️ Search Engine: We scanned hundreds of Google search result pages and ensured they will navigate you to the most appropriate content. This is especially important for the users that start from a search engine 4. ☀️ UX: Improved theming 5. 📈 Flytekit Plugins: We improved the documentation of the Flyte Plugins, extracting data directly from the plugin a. As a consequence we found code/package/conflict issues with some plugins, which we will follow up with authors/maintainers to update b. We will investigate how to make it easier to catch those issues during development of plugins and pre-submits and ensure high-quality content from the get go 6. 🔍 Search: Search integration complete 7. ♻️ Escape Hatch: Temporary fallback to the legacy site. Whenever your search results return a bad link, you will be offered the opportunity to (temporarily) jump to the old documentation. a. If you never see this feature, it means the work above worked! b. If you do, please report so we can make sure the new content is up and up. Please don't hesitate to let us know if some content is not available, not easy to find, or if something is not behaving as it should. Thanks for being part of the Flyte community!

This week in Flyte 📚 Documentation migration updates: • Link Maintenance: Actively using a linkchecker to identify and fix broken internal cross-references and external links across the site. • API Docs Fixes: Addressing issues with API documentation autogeneration; aiming to re-generate API docs once resolved (targeting completion next week). • Redirect Audit: Planning to audit the old Flytekit API reference section and improve redirects to new API docs (current redirects lead to the top of the new section, requiring manual in-site search). • Please use this discussion to report any docs issue 🌍 New Flytekit plugin: automate xarray/zarr data movement between tasks with the new plugin. Now available as

flytekitplugins-xarray-zarr

! ⚙️ Calling all GKE users! The GKE and Akvelon teams developed a Flyte on GKE guide and are looking for feedback. Add your comments in the thread or try out the guide!

📣 Flyte Monthly Contributors Spotlight Here's a roundup of this month's amazing contributors and their contributions: • @witty-alligator-81055 removed the grpcio upper bound in the flytekit library. • @gorgeous-waitress-5026 enhanced the flyteadmin OIDC configuration by allowing separate issuer URLs for token validation. • @cool-lifeguard-49380 upgraded the kubeflow training operator. • @rich-garden-69988 fixed async s3fs to handle the latest changes to flytefile. • Hsuan-Chen Chen added a user-defined builder image to imagespec and support for avoiding duplicated handler registration. • @clean-glass-36808 has been diligently reviewing PRs! 🙏 • Joe Polin added a check to detect extraneous arguments in the task decorator. • @brainy-carpenter-31280 upgraded Spark to 3.5.5 and added support for IPv6 and Iceberg. • @bored-beard-89967 added a plugin to support xarray object types, which persists the data to a zarr store. • @aloof-painting-18735 fixed a bug in Spark fast registration that caused an infinite loop due to recursive archiving. Huge thanks to everyone for your outstanding efforts! 🙌

🟢 Flyte community sync is live: ◦ PathomIQ sharing their journey and how they use Flyte to transform prostate cancer care ⚕️ ◦ Tuesday, 9:00am PT ◦ Join on LinkedIn or YouTube

Hi everyone: We're going live today at 10:00am PT! Parallelism options in Flyte and Union Hands-on session exploring the levels of parallelism you can achieve in Flyte, current limitations, and Union features like Actors or Map over Launchplans for additional efficiency. 💪🏽 No slide decks, no pitch, just live coding ➡️ Join on LinkedIn or YouTube Hopefully you can join and learn something new!

Cross posting - https://flyte-org.slack.com/archives/C0308A8TNAU/p1746735621409459

can someone add Flyte to this list - https://github.com/astral-sh/ruff/tree/2abcd86c57f8fafc219ea622d11d0984d639fba2?tab=readme-ov-file#whos-using-ruff

Hi everyone: The new Flyte docs repo is public! As you may have noticed, the Flyte docs were migrated to a new/common system, and the repo is now made public for anyone to contribute. Both Flyte and Union docs are now open to all. Changes will, of course, be done via pull request and will require approval of the code owners, but anyone in the community will be able to contribute. Contributor guides can be found here: https://www.union.ai/docs/flyte/community We'll be running an intro and Q&A during the next community sync (June 3) but drop your questions in this thread at anytime. Thank you!

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of this month’s amazing contributors and their contributions: • @microscopic-truck-17789 made `image_spec.tag` a cached property to avoid repeated hash computations. • @faint-pilot-24699 fixed an issue to allow cache policies to accept a list. • @cool-lifeguard-49380 added support for `labels` and `annotations` in the task decorator. • @clean-glass-36808 added support for configuring storage from a secret, enabled plumbing of pod affinity and topology spread constraints, and introduced customization of rollout strategy for flyte components. • Perttu Kärnä added support for configuring deployment annotations in the helm chart. • @redartera added the `--interruptible` option to `pyflyte run --remote`. • @bland-dress-83134 updated the default propeller raw output prefix to use the storage bucket name in the helm chart config. • @worried-airplane-87065, @gentle-tomato-480, @proud-glass-36655, and @echoing-account-76888 were active in helping others on Slack. Thank you all for pushing flyte forward with your awesome contributions! 🚀

Happening today at 9:00am PT 🙂 https://flyte-org.slack.com/archives/C02JMT8KTEE/p1748392003149539

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of this month’s amazing contributors and their contributions: • @faint-pilot-24699 fixed a bug where agent auto discovery conflicted with explicit task type mappings. • @clean-glass-36808 resolved issues with pod template overrides, cleaned up the workflow store interface, and has been actively supporting users on Slack. • @echoing-account-76888 added a signal watcher to copilot and has been helping out in the community. • @bitter-megabyte-57097 fixed dataclass deserialization for optional fields and added support for setting default resource requests/limits in pyflyte. • @gentle-tomato-480 and @proud-glass-36655 have been actively helping others on Slack. Thank you all for pushing flyte forward with your awesome contributions! 🚀

Dear Flyte Community, I know it’s unconventional, but I want to start by saying sorry. We’ve been quiet for a while, and for that, I want to apologize. The silence wasn’t neglect. We’ve been heads-down building something big. Today, I finally get to share a glimpse of what’s next. Flyte 2.0 is coming. This isn’t just an upgrade. Flyte 2.0 reimagines the platform as a fully dynamic orchestrator with Python-native authoring, letting you build agentic systems, ML pipelines, and AI applications. The same core principles of Flyte remain: modularity, composability, auto-caching, durability, versioning, parallel execution. But now we’re adding the flexibility and dynamism you’ve been asking for. And we’re staying true to what made Flyte special from the beginning: open source. That won’t change. Flyte 2.0 will be built in the open, and we want your feedback to shape its future, especially from those most actively using Flyte and our community already. What you need to know: On July 29th, I’m introducing the Flyte 2.0 vision in a virtual session. I’ll walk through the thinking behind Flyte 2.0. I’ll share what’s changing, what’s staying the same, and where we’re headed. We’ll also host “office hours” so our community can contribute to Flyte’s vision. Three asks for you: 1. RSVP here to join the Flyte 2.0 vision session (even if you can’t make it, we’ll send you the recording) 2. Stay tuned on LinkedIn for ways to get involved 3. Please like/share/comment on our Flyte 2.0 content on LinkedIn (this is so important for us as we grow our community) Thanks for being part of the journey. We can’t wait to build the future of AI infrastructure with you. With gratitude and excitement, Ketan Co-creator of Flyte CEO, Union.ai My LinkedIn