Skip to content

3.3.6 - One flow, many roads

Compare
Choose a tag to compare
@desertaxle desertaxle released this 24 Apr 19:25
· 103 commits to main since this release
01441af

Direct submission of workflows to dynamic infrastructure is in beta!

We're pleased to announce the beta release of new infrastructure decorators enabling the submission of workflows directly to dynamic infrastructure.

This feature enables you to easily execute workflows on various infrastructure environments without the need for multiple deployments or managing persistent workers. This simplifies workflow definitions and enhances portability.

Here's a small example of the new @kubernetes decorator in action:

from prefect import flow
from prefect_kubernetes import kubernetes

@kubernetes(work_pool="olympic")
@flow(result_storage="s3-bucket/remote-result-storage")
def my_k8s_flow():
    return "🏊‍♀️ Finished another lap!"

@flow
def parent_flow():
    return my_k8s_flow() # will run in a Kubernetes cluster via the 'olympic' work pool

print(my_k8s_flow()) # prints "🏊‍♀️ Finished another lap!"

Check out the docs for more information on using this new feature.

Feedback is very important for us to help refine this feature while it's in beta. Give it a try, and share your feedback with us by opening an issue!

Enhancements ➕➕

Bug Fixes 🐞

Development & Tidiness 🧹

Documentation 📓

  • Add initial documentation for submitting workflows directly to dynamic infrastructure by @desertaxle in #17861
  • Fix dead integration link by @zzstoatzz in #17831
  • Nginx sample config + note about client API key/auth string precedence by @ColinMaudry in #17810

New Contributors

Full Changelog: 3.3.5...3.3.6