a45d72d75d
* Add v2apis script in package.json * Generate typescript v2 api client. * Change api client codegen section in README Make it more clear: put the jar file in frontend folder. * Add v2 api codegen script in README. * Remove beta1 text to avoid confusion in README. * Format * Rename folder as apisv2beta1. Add apisv2beta1 in .eslintrc.yaml file * Change script from v2apis to apis:v2beta1 Remove unnecessary folder v2generated (move files to generated/apisv2beta1/ * Add the command for exporting jar file path to $PATH in README file. |
||
|---|---|---|
| .github | ||
| api | ||
| backend | ||
| components | ||
| contrib | ||
| docs | ||
| frontend | ||
| hack | ||
| manifests | ||
| proxy | ||
| samples | ||
| sdk | ||
| test | ||
| third_party | ||
| tools | ||
| .cloudbuild.yaml | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .isort.cfg | ||
| .pre-commit-config.yaml | ||
| .pylintrc | ||
| .readthedocs.yml | ||
| .release.cloudbuild.yaml | ||
| .style.yapf | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| OWNERS | ||
| README.md | ||
| RELEASE.md | ||
| ROADMAP.md | ||
| VERSION | ||
| developer_guide.md | ||
| go.mod | ||
| go.sum | ||
| mypy.ini | ||
| package-lock.json | ||
| package.json | ||
| release-status-check.png | ||
| requirements.txt | ||
| retry-release-on-tag.png | ||
| verify-retry-the-right-build.png | ||
README.md
Overview of the Kubeflow pipelines service
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:
- End to end orchestration: enabling and simplifying the orchestration of end to end machine learning pipelines
- Easy experimentation: making it easy for you to try numerous ideas and techniques, and manage your various trials/experiments.
- Easy re-use: enabling you to re-use components and pipelines to quickly cobble together end to end solutions, without having to re-build each time.
Installation
-
Install Kubeflow Pipelines from choices described in Installation Options for Kubeflow Pipelines.
-
⭐ [Alpha] Starting from Kubeflow Pipelines 1.7, try out Emissary Executor. Emissary executor is Container runtime agnostic meaning you are able to run Kubeflow Pipelines on Kubernetes cluster with any Container runtimes. The default Docker executor depends on Docker container runtime, which will be deprecated on Kubernetes 1.20+.
Documentation
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.
Refer to the versioning policy and feature stages documentation for more information about how we manage versions and feature stages (such as Alpha, Beta, and Stable).
Contributing to Kubeflow Pipelines
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.
Kubeflow Pipelines Community Meeting
The meeting is happening every other Wed 10-11AM (PST) Calendar Invite or Join Meeting Directly
Kubeflow Pipelines Slack Channel
Blog posts
- Getting started with Kubeflow Pipelines (By Amy Unruh)
- How to create and deploy a Kubeflow Machine Learning Pipeline (By Lak Lakshmanan)
- Kubeflow Pipelines meets Tekton (By Animesh Singh)
Acknowledgments
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. Additionally there is Tekton backend available as well. To access it, please refer to Kubeflow Pipelines with Tekton repository.