-
Notifications
You must be signed in to change notification settings - Fork 6.5k
[Doc] Convert configuring-autoscaling.ipynb back to markdown docs #54111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[Doc] Convert configuring-autoscaling.ipynb back to markdown docs #54111
Conversation
… docs Signed-off-by: Eagle Lo <eagle.lo@samsara.com>
Signed-off-by: Eagle Lo <eagle.lo@samsara.com>
…to markdown Signed-off-by: Eagle Lo <eagle.lo@samsara.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restored the previous markdown version from git history and updated it for KubeRay v1.4.0
This may miss some commits. You can check the commit history here:
https://github.com/ray-project/ray/commits/master/doc/source/cluster/kubernetes/user-guides/configuring-autoscaling.ipynb
Signed-off-by: Eagle Lo <eagle.lo@samsara.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rerun all steps in the doc with KubeRay v1.4.0 and correct any wrong information in the doc. Especially check for the resource names. Ping me again when you are done. Thanks!
### Step 3: Create a RayCluster custom resource with autoscaling enabled | ||
|
||
```bash | ||
kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/v1.3.0/ray-operator/config/samples/ray-cluster.autoscaler.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/v1.3.0/ray-operator/config/samples/ray-cluster.autoscaler.yaml | |
kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/v1.4.0/ray-operator/config/samples/ray-cluster.autoscaler.yaml |
|
||
# [Example output] | ||
# NAME READY STATUS RESTARTS AGE | ||
# raycluster-autoscaler-head-6zc2t 2/2 Running 0 107s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please manual rerun the whole doc with KubeRay v1.4.0. There are some resource name changes in v1.4.0. For example, the name of the head pod here should be raycluster-autoscaler-head
.
Signed-off-by: Eagle Lo <eagle.lo@samsara.com>
@MortalHappiness Hi! I've addressed your feedback and pushed the updates: 1. Fixed resource naming, 2. Updated to v1.4.0 URL, 3.Updated all references. |
Why are these changes needed?
This PR converts the configuring-autoscaling.ipynb notebook back to markdown documentation as part of the effort to remove doctests from documentation and improve maintainability.
Changes made:
configuring-autoscaling.ipynb
toconfiguring-autoscaling.md
raycluster-autoscaler-small-group-worker-xxxxx
autoscalerOptions.version: v2
configuration for KubeRay >= 1.4.0kind delete cluster
to cleanup stepsRelated issue number
Closes #54077
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.Manual Testing:
✅ All quickstart steps (1-8) have been manually tested and verified to work
Step 1: Create a Kubernetes cluster with Kind

Step 2: Install the KubeRay operator

Step 3: Create a RayCluster custom resource with autoscaling enabled

Step 4: Verify the Kubernetes cluster status

Step 5: Trigger RayCluster scale-up by creating detached actors



kubectl exec -it $HEAD_POD -- python3 /home/ray/samples/detached_actor.py actor1
kubectl exec -it $HEAD_POD -- python3 /home/ray/samples/detached_actor.py actor2
Step 6: Trigger RayCluster scale-down by terminating detached actors


Step 7: Ray Autoscaler observability

Step 8: Clean up
