community icon indicating copy to clipboard operation
community copied to clipboard

Proposal: Donate Kale to Kubeflow

Open StefanoFioravanzo opened this issue 1 month ago • 5 comments

Kale has a long history with Kubeflow, dating back to 2019. Kale provides the means to deploy Kubeflow pipelines directly from the Jupyter notebook UI, without ever leaving the IDE.

Kale is an essential part of the newly established ML Experience Working Group charter.

Kale was abandoned in 2022, but with the GSoC 25 program we updated the project to work on the most recent version of JupyterLab and Kubeflow Pipelines. We have now 6 active maintainers who are collaborating on the project, and an established roadmap for the next few months. You can find more details in the PR's doc.

Related issues:

  • https://github.com/kubeflow/community/issues/730
  • https://github.com/kubeflow/community/issues/808

cc @ederign

StefanoFioravanzo avatar Nov 09 '25 10:11 StefanoFioravanzo

cc @kubeflow/kubeflow-steering-committee

StefanoFioravanzo avatar Nov 09 '25 11:11 StefanoFioravanzo

In general I like the idea and if we build this by default into Jupyterlabs it is also integrated into Kubeflow platform. But right now it is still lacking regarding basic Kubernetes standards https://github.com/kubeflow-kale/kale/issues/501 and automated tests and releases. I would like to see the basic stuff covered such that we know that it is long-term maintainable.

juliusvonkohout avatar Nov 10 '25 08:11 juliusvonkohout

@juliusvonkohout thank you so much for the feedback and for pointing out https://github.com/kubeflow-kale/kale/issues/501 . We are going to fix it.

Regarding releases and automated tests we are working towards them for a 2.0 release: https://github.com/kubeflow-kale/kale/issues/457

ederign avatar Nov 13 '25 12:11 ederign

@juliusvonkohout thank you so much for the feedback and for pointing out kubeflow-kale/kale#501 . We are going to fix it.

Regarding releases and automated tests we are working towards them for a 2.0 release: kubeflow-kale/kale#457

@ederign I think you need https://github.com/kubeflow/pipelines/issues/12205 and help form @hbelmiro @HumairAK etc. to set a proper securitycontext. CC @franciscojavierarceo

juliusvonkohout avatar Dec 02 '25 14:12 juliusvonkohout

I approve moving forward with Kale.

franciscojavierarceo avatar Dec 17 '25 16:12 franciscojavierarceo

+1 after getting clarity on impact for graduation https://cloud-native.slack.com/archives/C08M8L74NAJ/p1765898532002049

terrytangyuan avatar Dec 17 '25 16:12 terrytangyuan

Thank you @kubeflow/kubeflow-steering-committee for the continued support, we can't wait to release the next version of Kale under Kubeflow's umbrella.

Can anyone of you approve the PR, so that we can initiate the migration phase?

StefanoFioravanzo avatar Dec 18 '25 09:12 StefanoFioravanzo

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

google-oss-prow[bot] avatar Dec 18 '25 12:12 google-oss-prow[bot]

Aaaaand it's done :D

https://github.com/kubeflow/kale

StefanoFioravanzo avatar Dec 19 '25 12:12 StefanoFioravanzo