kubeflow/pipelines

Machine Learning Pipelines for Kubeflow

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 11 minutes ago
Added to GitGenius on June 18th, 2024
Created on May 12th, 2018
Open Issues & Pull Requests: 366 (+0)
GitHub issues: Enabled
Number of forks: 2,145
Total Stargazers: 4,236 (+0)
Total Subscribers: 95 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 46.0 hours
Mean response time: 168.9 days
90th percentile: 660.2 days
Tracked items: 1,004

Maintainer activity

114 people did triage or write work on this repository in the last 12 months.

At least 6% of pipelines's 114 maintainers work at Red Hat. 28 say where they work, and 7 of those are Red Hat.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 18% of issues opened in the past year have never received a reply. 79% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "area/testing" is answered fastest, typically in under an hour, while "area/components" waits about 5 weeks. Almost all tracked open issues have seen activity in the last three months. Only 55% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 229
New in 7 days: 18
Closed in 7 days: 19
Avg open age: 151 days
Stale 30+ days: 120
Stale 90+ days: 14

Recent activity

Opened in 7 days: 17
Closed in 7 days: 15
Comments in 7 days: 28
Events in 7 days: 72

Top labels

  • kind/bug (1,805)
  • lifecycle/stale (1,404)
  • kind/feature (982)
  • area/backend (918)
  • area/sdk (670)
  • area/frontend (607)
  • status/triaged (568)
  • priority/p1 (334)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kubeflow Pipelines is a machine learning workflow orchestration system built on Kubernetes that enables users to construct, deploy, and manage end-to-end ML workflows. Written primarily in Python, it serves as a core component of the Kubeflow ML toolkit and provides the Kubeflow Pipelines SDK for building reusable ML pipelines that can run on Kubernetes clusters with portability and scalability.

The repository addresses three primary objectives outlined in its documentation: enabling end-to-end orchestration of ML pipelines, facilitating easy experimentation through trial and experiment management, and promoting component and pipeline reusability to accelerate solution development. Users can install Kubeflow Pipelines either as part of the complete Kubeflow Platform or as a standalone service. The system has evolved to support modern Kubernetes environments by defaulting to the Emissary Executor from version 1.8 onward, which is container runtime agnostic and works with any Kubernetes-supported container runtime, replacing the deprecated Docker container runtime that was incompatible with Kubernetes 1.20 and later.

The project maintains compatibility with specific dependency versions including Argo Workflows v3.7 and v4.0, and MySQL v8. Under the hood, Kubeflow Pipelines leverages Argo Workflows to orchestrate Kubernetes resources, a relationship the project acknowledges and credits in its documentation. The repository includes comprehensive documentation covering SDK usage, API specifications, and Python SDK references, along with architectural details and developer guides for contributors.

The project maintains an active community with biweekly meetings held on Wednesdays from 10-11 AM PST and a dedicated Slack channel on the Cloud Native Computing Foundation workspace. The repository includes optional developer tooling through a just command runner that wraps existing make targets for convenience, though all CI and release workflows continue to use the underlying make infrastructure. Contributing guidelines and developer setup documentation are provided to facilitate community participation in the project's ongoing development and maintenance.