ciao
ciao copied to clipboard
[UX] non-kubeflow backend
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind feature
Now we are required to install kubeflow to use ciao, to make it easier for people to get start, i think we can do:
- use kubernetes job backend
- only install required operators (can be installed via helm charts)
wdyt? @gaocegege
Actually, now we work with selected operators (pytorch and tf), there is no need to install all packages in kubeflow for ciao.
As for kubernetes job backend, we can implement while I think it is not in high priority.
yeah, but the installation guide asks me to install kubeflow..
I am not sure if we will support katib in the future, thus I wrote that.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/priority p3