Kubeflow is a machine learning (ML) toolkit that is dedicated to making deployments of ML workflows on Kubernetes simple, portable, and scalable.
Kubeflow pipelines are reusable end-to-end ML workflows built using the Kubeflow Pipelines SDK.
The Kubeflow pipelines service has the following goals:
Kubeflow Pipelines can be installed as part of the Kubeflow Platform. Alternatively you can deploy Kubeflow Pipelines as a standalone service.
The Docker container runtime has been deprecated on Kubernetes 1.20+. Kubeflow Pipelines has switched to use Emissary Executor by default from Kubeflow Pipelines 1.8. Emissary executor is Container runtime agnostic, meaning you are able to run Kubeflow Pipelines on Kubernetes cluster with any Container runtimes.
| Dependency | Versions |
|---|---|
| Argo Workflows | v3.5, v3.7 |
| MySQL | v8 |
Get started with your first pipeline and read further information in the Kubeflow Pipelines overview.
See the various ways you can use the Kubeflow Pipelines SDK.
See the Kubeflow Pipelines API doc for API specification.
Consult the Python SDK reference docs when writing pipelines using the Python SDK.
Check out our AI Powered repo documentation on DeepWiki.
:warning: Please note, this is AI generated and may not have completely accurate information.
Before you start contributing to Kubeflow Pipelines, read the guidelines in How to Contribute. To learn how to build and deploy Kubeflow Pipelines from source code, read the developer guide.
just command runnerFor local developer convenience, this repository includes an optional just command runner at the repo root. It provides short aliases for existing make targets and does not replace any CI or release workflows.
To use it, install just and run, for example:
just # list available recipes
just backend-test
just backend-images
Notes:
just recipes are thin wrappers around existing make targets (for example, make -C backend/src/v2 test).just build or just test recipe; heavy or Docker-building flows are exposed only via explicitly named recipes such as backend-images.The Kubeflow Pipelines Community Meeting occurs every other Wed 10-11AM (PST).
We also have a slack channel (#kubeflow-pipelines) on the Cloud Native Computing Foundation Slack workspace. You can find more details at https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels
Details about the KFP Architecture can be found at Architecture.md
Kubeflow pipelines uses Argo Workflows by default under the hood to orchestrate Kubernetes resources. The Argo community has been very supportive and we are very grateful.
$ claude mcp add pipelines \
-- python -m otcore.mcp_server <graph>