kubeflow/sdk

Universal Python SDK to run AI workloads on Kubernetes

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

kubeflow/sdk has 150+ stars and 250+ forks on GitHub, is written in Python, and was last pushed on Oct 19, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Added to GitGenius on October 15th, 2026
Created on April 23rd, 2025
Open Issues & Pull Requests: 294 (+0)
GitHub issues: Enabled
Number of forks: 292
Total Stargazers: 155 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 5.1 days
90th percentile: 6.3 days
Tracked items: 241

Maintainer activity

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

At least 5% of sdk's 102 maintainers work at Red Hat. 33 say where they work, and 5 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 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 66% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 19% of tracked open issues have had no activity in three months. Only 45% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 7
Closed in 7 days: 3
Avg open age: 109 days
Stale 30+ days: 42
Stale 90+ days: 15

Recent activity

Opened in 7 days: 5
Closed in 7 days: 3
Comments in 7 days: 7
Events in 7 days: 30

Top labels

  • kind/feature (100)
  • needs-triage (68)
  • kind/bug (67)
  • area/spark (57)
  • help wanted (45)
  • good first issue (44)
  • lifecycle/stale (24)
  • area/trainer (19)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kubeflow SDK is a Python SDK that provides unified APIs to run AI workloads on Kubernetes without requiring users to learn Kubernetes directly.

The tool addresses the complexity of deploying and managing machine learning workloads across Kubernetes clusters by abstracting away infrastructure concerns behind consistent Python APIs. It unifies access to multiple Kubeflow ecosystem projects through a single interface, allowing developers to write code once and scale it from local development environments to large production clusters without changing their application logic. The SDK supports distributed training frameworks like PyTorch and JAX, hyperparameter optimization, LLM fine-tuning, and data processing via Spark Connect, while also providing model registry and pipeline management capabilities.

Teams should adopt this tool if they want to reduce friction between local development and production deployment of AI workloads on Kubernetes. It suits projects that need to scale from prototyping to production without rewriting code for different environments. The SDK is particularly valuable for teams building with PyTorch, JAX, or Hugging Face models, or those requiring distributed training and hyperparameter optimization. Local development is a first-class concern, with support for Docker, Podman, and Python subprocess backends alongside the production Kubernetes backend, so developers can iterate without cluster access.

The project maintains active development with regular releases introducing new capabilities such as Spark and Model Registry client support. Development appears focused on expanding the ecosystem integrations and improving the developer experience across different deployment scenarios. The team actively solicits user feedback to guide future direction.