-
Notifications
You must be signed in to change notification settings - Fork 772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with Kubeflow pipelines #25
Comments
@BAlmeidaS I mentioned this integration with kubeflow in issue Support for Airflow and Kubernetescomment. I really thought that metaflow integration with kubeflow reduce work in integration on Kubernetes. |
Yes @SteNicholas I saw the issue, I decided opened mine anyway because I thought that one thing is integration with k8s and deploy an orchestrated pipeline with docker. Another thing is to deploy a Kubeflow pipelines targz (which is similar but not the same thing). |
Thanks for opening the issue, @BAlmeidaS . Issues like these are really informative as we go about planning our roadmap. |
@BAlmeidaS @ |
Kubeflow's Pipeline features are a little different from Metaflow's DAG features. Kubeflow supports conditional Steps in workflows. Metaflow doesn't have support for conditional flows. |
Kubeflow supports conditional branching concept that Metaflow doesn't. Metaflow could compile to Kubeflow via an intermediate representation (kubeflow/pipelines#3703) |
@talebzeghmi I responded in this other thread. Our current integration to AWS Step Functions' State Machine Representation is in PR #204 . |
The reference implementation for AWS Step Functions is available here now. This should serve as a good starting point for any other scheduler integration. |
Sorry for the enormous delay to answer this, I lost the tracking about this project. I was very excited about it when it launched but we developed our own solution to integrate with kfp. Answering @Jeffwan, IMO we could use kfp to deploy via metaflow. User may not notice that she is deploying a pipeline in kubeflow, even metaflow not having some features that kubeflow pipelines has. What you guys think about it?? |
Refactor foreach implementation * change recursive dfs sort to none-recursive dfs * split Step.task() into separate ..._task() functions
First things first, thanks to open this project!! We are working in a very similar project, and Metaflow is going to help us a lot.
Do you plan to create a kind of integration with Kubeflow Pipelines? For us, this is very helpful to deploy these pipelines in our production environment.
The text was updated successfully, but these errors were encountered: