Am curious if this feature coming soon this month/next month, am eagerly waiting for sometime? 🙂 https://outerbounds-community.slack.com/archives/C020U025QJK/p1668793150048639?thread_ts=1668768421.346539&cid=C020U025QJK

hopefully this month finally - early next month at the latest 🙏

yes we are adventurous !!

awesome! Btw, initially events work with Argo Workflows only. Is it ok?

hm... we're not using the kubernetes approach

correct, sadly. An AWS-native approach would most likely need to rely on EventBridge which is a trickier beast. We wanted to start with a platform we can control better and then based on those learnings expand the footprint, if there's demand for it

thanks for clarifying, this helps us reconsider a kubernetes setup of using metaflow

if you want to create a small test deployment using EKS, we can help get event triggering running on it

I can safely and confidently say that we have a demand for this :-)

+1 super excited for this feature and I'm sure there will tons of demand across the infra flavors! For those currently using the AWS-native stack, I'm curious how feasible the following might be: • Deploy the EKS stack side-by-side with the existing AWS infra, allowing people to gradually shift workflows from using

@batch

to

@kubernetes

and likewise from SFN to Argo. • Features like event triggering would only be available to workflows using/migrated onto the EKS stack of tools • Hopefully can point both stacks to the same metadata service / UI for shared lineage Would this be doable or would shifting to EKS require a more substantial one-time migration?

@fresh-laptop-72652 - yep - this approach will totally work

excellent