
This PR Adds a warning about a known issue to the KubeRay section of the Ray docs. Updates the description of the feature state of KubeRay integration. Adds some links to the KubeRay docs.
4.9 KiB
Deploying with KubeRay
[KubeRay](https://github.com/ray-project/kuberay) is a set of tools for running Ray on Kubernetes.
It has been used by some larger corporations to deploy Ray on their infrastructure.
Going forward, we would like to make this way of deployment accessible and seamless for
all Ray users and standardize Ray deployment on Kubernetes around KubeRay's operator.
While KubeRay has been used in production to manage large Ray deployments, certain integrations
are still under development -- in particular, KubeRay's autoscaling functionality is alpha.
It is still valid to use the existing [Kubernetes integration](kubernetes.rst) hosted in the Ray repository for running Ray on Kubernetes. However, if you would like to try the KubeRay integration out, this documentation is for you! We would love your feedback as a [Github issue](https://github.com/ray-project/ray/issues) including `[KubeRay]` in the title.
You may also wish to check out the [KubeRay repository's documentation](https://ray-project.github.io/kuberay/).
Here we describe how you can deploy an autoscaling Ray cluster on KubeRay. The following instructions are for Minikube but the deployment works the same way on a real Kubernetes cluster. You need to have at least 4 CPUs to run this example. First we make sure Minikube is initialized with
minikube start
Now you can deploy the KubeRay operator using
./ray/python/ray/autoscaler/kuberay/init-config.sh
kubectl create -k "ray/python/ray/autoscaler/kuberay/config/default"
Note `kubectl apply` will not work in the above command. `kubectl create` is required. See [KubeRay issue #271](https://github.com/ray-project/kuberay/issues/271).
You can verify that the operator has been deployed using
kubectl -n ray-system get pods
Now let's deploy a new Ray cluster:
kubectl create -f ray/python/ray/autoscaler/kuberay/ray-cluster.complete.yaml
Using the autoscaler
Let's now try out the autoscaler. We can run the following command to get a Python interpreter in the head pod:
kubectl exec `kubectl get pods -o custom-columns=POD:metadata.name | grep raycluster-complete-head` -it -c ray-head -- python
In the Python interpreter, run the following snippet to scale up the cluster:
import ray.autoscaler.sdk
ray.init("auto")
ray.autoscaler.sdk.request_resources(num_cpus=4)
The example config ray-cluster.complete.yaml specifies rayproject/ray:8c5fe4
as the Ray autoscaler image. This image carries the latest improvements to KubeRay autoscaling
support. This autoscaler image is confirmed to be compatible with Ray versions >= 1.11.0.
Once Ray autoscaler support is stable, the recommended pattern will be to use the same
Ray version in the autoscaler and Ray containers.
Uninstalling the KubeRay operator
You can uninstall the KubeRay operator using
kubectl delete -f "ray/python/ray/autoscaler/kuberay/kuberay-autoscaler-rbac.yaml"
kubectl delete -k "ray/python/ray/autoscaler/kuberay/config/default"
Note that all running Ray clusters will automatically be terminated.
Further details on Ray autoscaler support.
Check out the KubeRay documentation for more details on Ray autoscaler support.
Developing the KubeRay integration (advanced)
Developing the KubeRay operator
If you also want to change the underlying KubeRay operator, please refer to the instructions
in the KubeRay development documentation. In that case you should push the modified operator to your docker account or registry and
follow the instructions in ray/python/ray/autoscaler/kuberay/init-config.sh
.
Developing the Ray autoscaler code
Code for the Ray autoscaler's KubeRay integration is located in ray/python/ray/autoscaler/_private/kuberay
.
Here is one procedure to test development autoscaler code.
- Push autoscaler code changes to your fork of Ray.
- Use the following Dockerfile to build an image with your changes.
# Use the latest Ray master as base.
FROM rayproject/ray:nightly
# Invalidate the cache so that fresh code is pulled in the next step.
ARG BUILD_DATE
# Retrieve your development code.
RUN git clone -b <my-dev-branch> https://github.com/<my-git-handle>/ray
# Install symlinks to your modified Python code.
RUN python ray/python/ray/setup-dev.py -y
- Push the image to your docker account or registry. Assuming your Dockerfile is named "Dockerfile":
docker build --build-arg BUILD_DATE=$(date +%Y-%m-%d:%H:%M:%S) -t <registry>/<repo>:<tag> - < Dockerfile
docker push <registry>/<repo>:<tag>
- Update the autoscaler image in
ray-cluster.complete.yaml
Refer to the Ray development documentation for further details.