bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
9.05k stars 9.22k forks source link

Helm Chart for kubeflow (Machine Learning) #15177

Closed Syntax3rror404 closed 6 months ago

Syntax3rror404 commented 1 year ago

Name and Version

bitnami/kubeflow 1.6.1

What is the problem this feature will solve?

Machine learning is becoming increasingly important. The platforms to build the complex models are getting more and more complex. One of these platforms is kubeflow, which already provides kustomize deployments. The problem is with this 1000 files it is absolutely infinitely hard to set up and maintain this platform. A Helm chart would completely solve this problem.

-> GitHub Repo of kubeflow: https://github.com/kubeflow/kubeflow -> GitHub Repo of the manifests https://github.com/kubeflow/manifests

It would be absolutely amazing if you had a helm chart for this.

What is the feature you are proposing to solve the problem?

A helm chart for kubeflow

What alternatives have you considered?

No response

carrodher commented 1 year ago

Thanks for your suggestion!

We will check it internally and evaluate the feasibility of adding this new product to the catalog; due to limited resources, this process could take some time. In the meantime and to prevent the stale bot from closing this issue, we will add the 'on-hold' label.

Syntax3rror404 commented 1 year ago

@carrodher sounds good thanks a lot :)

jesperrix commented 1 year ago

Are there any updates to adding kubeflow as a helm chart? It would be amazing 🤩

carrodher commented 1 year ago

Unfortunately, it is still in the queue to be analyzed in deep since it's a complex solution.

github-actions[bot] commented 1 year ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

Syntax3rror404 commented 1 year ago

ping (for bot)

thesuperzapper commented 12 months ago

For those watching this thread, there is an existing "helm-like" option for deploying Kubeflow, it's called deployKF.

It might meet your needs.

DreamingRaven commented 12 months ago

Sorry @thesuperzapper, I don't want ArgoCD plugins / bins, I also don't want a mass of manifests that are difficult to maintain or could introduce write errors. I want auditable charts that I can modify and maintain security with standard k8s tooling. If everything needed ArgoCD plugins it would become very difficult to maintain compliance and prevent supply chain attacks. I also want to integrate KF with the clusters I run not the other way around. A core helm chart suits my use case, which I then integrate with my existing setups declaratively like auth, storage, backups, service mesh etc. I don't want to deploy KF I want to integrate with, and maintain clusters that have KF. Deployment is the easy part! Otherwise the KF manifests / kustomize repo would be sufficient already.

Syntax3rror404 commented 12 months ago

@thesuperzapper Thank you for your response. However, for a production cluster, I am looking for a solution that aligns with the best practices in the Kubernetes universe, preferably a well-structured umbrella Helm chart.

DeployKF seems more like a makeshift workaround rather than a practical, long-term solution.

kirkpabk commented 9 months ago

(ping)

Syntax3rror404 commented 9 months ago

Hello @carrodher are there any news regarding this feature? It's been a year now since I open this issue.

There is a whole ML community which using kubeflow which waiting for a helm chart. Again if bitnami have a helm chart for this, this would be awesome!!

Thank you again for your time :)

carrodher commented 9 months ago

Hi, at this moment and given other tasks the team is working on, we can't find the bandwidth to work on such as complex solution like MLFlow. We are adding different applications for the ML/AI ecosystem. We'll have this application in mind for the future.

carrodher commented 6 months ago

Hi, unfortunately after an internal review, and due to other priorities, this solution was not considered to be added to the catalog in the short/mid-term.

We apologize for the inconvenience. We will be sure to reconsider it in the future.

Thanks for your suggestion!