-
Notifications
You must be signed in to change notification settings - Fork 137
is kfctl dead? #501
Comments
@speaknowpotato thanks for your question. As far as I know, no one in the Community is developing or supporting kfctl. Some systems and users still use it but there isn't any support. The manifest docs do say...."Starting from Kubeflow 1.3, all components should be deployable using kustomize only." but maybe we need to be more explicit about kfctl and update the kfctl repo. We discussed this over several releases 1.2, 1.3 and 1.4. Is your concern that folks will use kfctl because we are not explicit on the kfctl repo ? @kubeflow/wg-manifests-leads and @shannonbradshaw Do you have any comments or proposed fixes here? /area docs |
@jbottum thanks for your quick response. |
Hello people, so, what I understood is that this project should not be used anymore, right? The instructions for installation in Azure are not updated then, since it points to this tool. |
@64J0 @speaknowpotato you are correct that However, I imagine that deployKF Repo: https://github.com/deployKF/deployKF |
@zijianjoy can we please archive the |
Alternatively, @james-jwu and @chensun should have permission to archive this repo. |
Great, thanks for sharing @thesuperzapper. I agree that this repository must be archived to avoid mistakes in the future. |
it seems that kfctl is dead,
shall we go to https://github.com/kubeflow/manifests to install kubeflow instead?
is there any official announcement from the Kubeflow community?
Does anyone have thoughts?
The text was updated successfully, but these errors were encountered: