[Docs] Update KubeRay & Volcano integration document #59636
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the KubeRay & Volcano integration documentation. The changes correctly remove all references to the deprecated ray.io/scheduler-name: volcano label, which is no longer needed for scheduler configuration. The documentation is updated with a clear note explaining this change and now reflects the current practice of configuring the scheduler at the operator level. The PR also beneficially adds documentation for new Volcano labels related to network topology and clarifies the gang scheduling behavior with autoscaling. The updates are accurate and improve the clarity of the document for users.
|
Hi @win5923 @Future-Outlier , please take a look when you have a chance. Thank you! |
seanlaii
changed the title
Signed-off-by: seanlaii <qazwsx0939059006@gmail.com>
seanlaii
force-pushed
the
update-volcano-new
branch
from
440fee3 to
f29adb8
Compare
ray-gardener
bot
added
docs
| ``` | ||
|
|
||
| You can also be provide the following labels in the RayCluster metadata: | ||
| You can also provide the following labels in the RayCluster and RayJob metadata: |
There was a problem hiding this comment.
We currently don't support RayService IIUC. I can help if we would like to support it.
Future-Outlier
left a comment
Future-Outlier
left a comment
There was a problem hiding this comment.
cc @win5923 to take a look, thank you!
2 participants
Description
Previously, the
ray.io/scheduler-namelabel was used to determine the scheduler for KubeRay CRDs. However, with the adoption of the new scheduler framework, the scheduler name is now configured via the controller configuration,--batch-scheduler, and the label is no longer needed.Therefore, we can remove the information related to
ray.io/scheduler-nameto avoid ambiguity.Related issues
Related to ray-project/kuberay#4305
Additional information