You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the code linked, if kube_pod_manager == ray and kube_pod_manager_non_root == true, then a k8s admin or super user needs to install a namespaced or clusterwide ray operator and the raycluster crd for the user for this to function, is that correct? If so, where is this documented, or where should it be documented relative to the existing org/repo structure?
KUBE_POD_MANAGER_NON_ROOT applies to any situation where we don't want to assume root access. Currently, this applies to the "keep it simple" and "my admin will install mcad" paths.
re: how we document this, good question. i'll need to cogitate.
question
In the code linked, if kube_pod_manager == ray and kube_pod_manager_non_root == true, then a k8s admin or super user needs to install a namespaced or clusterwide ray operator and the raycluster crd for the user for this to function, is that correct? If so, where is this documented, or where should it be documented relative to the existing org/repo structure?
code lines
store/guidebooks/ml/ray/start/kubernetes/install-via-helm.sh
Lines 24 to 35 in 569c4ad
store/guidebooks/ml/ray/start/kubernetes/install-via-helm.sh
Line 79 in 569c4ad
The text was updated successfully, but these errors were encountered: