Skip to content

Donating KubeRay to CNCF #65900

Description

@richardliaw

KubeRay was originally co-developed and maintained by open-source contributors across multiple organizations (including Anyscale, Google, Microsoft, ByteDance, and AWS).

While commercial vendors offer managed Ray or AI platform services that utilize KubeRay upstream, KubeRay operates strictly as a vendor-neutral, community-driven Kubernetes operator.

Donating KubeRay to the CNCF will ensure long-term governance neutrality, encouraging broader cross-cloud and enterprise contribution without single-vendor control.

Why CNCF?
Neutral Infrastructure Governance: As Kubernetes becomes the defacto platform for AI/ML workloads, KubeRay serves as a critical control plane link. CNCF stewardship guarantees vendor-neutral governance and standard IP management (Apache 2.0).

Deep Ecosystem Collaboration: Bringing KubeRay into the CNCF facilitates tighter co-development with related cloud-native scheduling, observability, and storage projects (e.g., Kueue, Prometheus, Jaeger, Argo Workflows).

Enterprise Confidence: End-users deploying mission-critical AI/ML pipelines at scale benefit from CNCF's operational maturity, security audits, and community standards.

Process
As part of this process, we will need to move KubeRay into its own organization outside of ray-project.

This issue is to publicly document parent project maintainer consensus approving the move out of the ray-project organization to become a separate CNCF project.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

coreIssues that should be addressed in Ray CoredocsAn issue or change related to documentationquestionJust a question :)tech-debtThe issue that's due to tech debt

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions