Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal: Donate the MPI-Operator.V2 to kubernetes-sigs #557

Closed
wants to merge 3 commits into from
Closed

Proposal: Donate the MPI-Operator.V2 to kubernetes-sigs #557

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e413d78
Proposal: Donate the MPI-Operator.V2 to kubernetes-sigs
ArangoGutierrez Mar 11, 2022
503cbbd
Apply suggestions from code review
ArangoGutierrez Mar 14, 2022
e63eb1e
Add https://github.com/kubeflow/community/pull/557#discussion_r825989622
ArangoGutierrez Mar 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions proposals/donate-mpi-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Donate MPI-Operator.v2 repo to kubernetes-sigs
Donate the kubeflow/mpi-operator to a more generic/neutral place (e.g. K8s-sigs) where this project could be beneficial to more people, not limiting to ML-specific workloads. Especially given that now kubeflow/training-operator gets heavier, people should be given the option to only install MPI Operator for their use cases.

During kubernetes SIG-APPS (Mar-7 2022) [call]((https://github.com/kubernetes/community/tree/master/sig-apps#meetings)) the topic was proposed to the SIG chairs, and they agreed to sponsor the repo.

- [Motivation](#motivation)
- [Goals](#goals)
- [Non-Goals](#non-goals)
- [Process](#process)
- [Alternatives Considered](#alternatives-considered)

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

_Status_

* 2022-03-11 - Proposed

## Motivation
Kubeflow currently is moving to an [Unified operator](https://github.com/kubeflow/training-operator)
The motivation is to encourage non-training users (like HPC) to use and contribute to mpi-operator, without having to install or learn about kubeflow's training-operator.

## Goals
* Migrate repo kubeflow/mpi-operator/v2 to kubernetes-sigs/mpi-operator
* Kubeflow declares the kubernetes-sigs/mpi-operator as a dependency
* The Kubeflow Training WG continues to be involved in the mpi-operator development, proposing and implementing changes that align with the needs of AI/ML.

## Non-Goals
* Migrate kubeflow/mpi-operator.v1

## Process

* Donate kubeflow/mpi-operator to kuberenetes-sigs as detailed [here](https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories), being tracked [here](https://github.com/kubeflow/mpi-operator/issues/459)
* Close https://github.com/kubeflow/training-operator/issues/1479
* Close https://github.com/kubeflow/mpi-operator/issues/422
* Re-org the repo to remove dependency on kubeflow/common
* Cut a first release under k8s-sigs

## Alternatives Considered
Continue to maintain the MPI-Operator as a stand alone project unregarless of the development of the universal operator, for non AI/ML use cases.