-
Notifications
You must be signed in to change notification settings - Fork 706
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.
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
Add Helm Charts for Kubeflow Training V2 #1197
Comments
I would like to work on this issue. Since I'm new here, can someone guide me? |
Thanks, @goat023 You can have a look at other operator's helm chart, like tidb-operator or etcd-operator. It should be similar to them. |
There's also helm chart for mpi-operator for reference but probably needs some update as well: https://github.com/kubeflow/mpi-operator/tree/master/hack/helm/mpi-operator |
Thanks, I'll try |
where can I get the maintainer's name and email address for this repo |
@goat023 Hi, is there any progress? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Do you still need one? |
Inorder to ensure that helm charts are in sync, we can add one extra check in Github Actions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
More and more Kubernetes projects are moved toward Helm charts for the deployment:
I think, we should consider to create Helm Chart for at least Kubeflow Training V2 |
/remove-lifecycle stale |
I strongly agree with adding a Helm chart for the training operator, and I am willing to maintain it, drawing on my experience with the Spark operator Helm chart. |
Great, thank you @ChenYi015! |
+1 as long as we can sustain the maintenance |
No description provided.
The text was updated successfully, but these errors were encountered: