[Feature][Doc] Kubeflow integration #937
Conversation
kevin85421
requested review from
architkulkarni,
DmitriGekhtman,
Jeffwan and
gvspraveen
| ``` | ||
|
|
||
| ## Step 2: Install Kubeflow v1.6-branch | ||
| * This example installs Kubeflow with the [v1.6-branch](https://github.com/kubeflow/manifests/tree/v1.6-branch). |
There was a problem hiding this comment.
Why do we need the 1.6 branch specifically? Would be good to add a brief comment
There was a problem hiding this comment.
Kubeflow is very sensitive to the Kubernetes version and the Kustomize version, so some instructions in this document may not work with other releases. In addition, some components will be renamed in future Kubeflow releases, and I am not familiar with the Kubeflow community's plan.
| ``` | ||
| * This step uses `rayproject/ray:2.2.0-py38-cpu` as its image. Ray is very sensitive to the Python versions and Ray versions between the server (RayCluster) and client (JupyterLab) sides. This image uses: | ||
| * Python 3.8.13 | ||
| * Ray 2.2.0 |
There was a problem hiding this comment.
I suppose we can use 2.3.0 now, but if it will require a lot more manual testing then it might not be worth it.
There was a problem hiding this comment.
It is a huge effort. Ray client is very sensitive to the Python versions and Ray versions. Sometimes I use the same Ray commit in the JupyterLab instance and in the RayCluster's docker image, but it is still not compatible.
Signed-off-by: Kai-Hsun Chen <kaihsun@apache.org>
Co-authored-by: Archit Kulkarni <architkulkarni@users.noreply.github.com> Signed-off-by: Kai-Hsun Chen <kaihsun@apache.org>
Good point. I forget about it. We can reorganize the website later. |
Kubeflow integration
Why are these changes needed?
Use Kubeflow as a solution of interactive prototyping environment (JupyterLab).
Related issue number
Closes #725
Part of #502. The issue includes JupyterLab, access control, and authentication. This PR only includes JupyterLab.
Checks