Skip to content

Conversation

@seanlaii
Copy link
Contributor

@seanlaii seanlaii commented Dec 22, 2025

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines

@volcano-sh-bot volcano-sh-bot added the kind/documentation Categorizes issue or PR as related to documentation. label Dec 22, 2025
@volcano-sh-bot
Copy link
Collaborator

Welcome @seanlaii! It looks like this is your first PR to volcano-sh/website 🎉

@gemini-code-assist
Copy link

Summary of Changes

Hello @seanlaii, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces new documentation that outlines the integration of KubeRay with Volcano, a powerful batch scheduler for Kubernetes. The added guide explains how this integration, available since KubeRay v1.5.1, enables advanced scheduling capabilities such as gang scheduling and network topology awareness for Ray workloads, thereby optimizing resource allocation and performance for distributed AI/ML applications running on Kubernetes.

Highlights

  • New Documentation: A comprehensive guide has been added detailing the integration of KubeRay with Volcano, a batch scheduler for Kubernetes.
  • Volcano Integration Details: The documentation explains how KubeRay v1.5.1 and later versions support gang scheduling and network topology-aware scheduling for RayJob and RayCluster resources through Volcano.
  • Configuration and Examples: The guide includes prerequisites, supported labels for configuring Volcano scheduling (e.g., ray.io/scheduler-name: volcano), and practical deployment examples for both RayCluster and RayJob.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@volcano-sh-bot volcano-sh-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 22, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds documentation for integrating KubeRay with Volcano. The new page provides a comprehensive guide, including an introduction to KubeRay, setup instructions, configuration details, and example deployments for RayCluster and RayJob. The documentation is well-structured and clear. I have one suggestion to adjust the menu weight to avoid conflicts with existing documentation pages.

@seanlaii
Copy link
Contributor Author

Hi @win5923 @JesseStutler , could you take a look when you have a chance? Thank you!

@seanlaii seanlaii force-pushed the kuberay-eco branch 3 times, most recently from cccd97a to f3dc97a Compare December 23, 2025 04:01
@JesseStutler
Copy link
Member

@seanlaii Does this pr have rendering problem? I see that all the netlify CI failed

@JesseStutler
Copy link
Member

@seanlaii BTW, could you also add a Chinese version doc? Thanks!

# test-cluster-0-head-jj9bg 1/1 Running 0 36s
```

##### RayJob Example
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also add vcjob example? https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_ray_plugin.md, in volcano v1.13 version, we have also supported using vcjob to create raycluster

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, added.

@seanlaii
Copy link
Contributor Author

@seanlaii Does this pr have rendering problem? I see that all the netlify CI failed

I think it might be rate limited. It is working now.

@seanlaii
Copy link
Contributor Author

@seanlaii BTW, could you also add a Chinese version doc? Thanks!

Sure, I will add it once the English version is reviewed. Please let me know if you have any feedback on the English version. Thanks!

cc @win5923

Copy link

@win5923 win5923 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for the KubeRay part, thanks for your effort!

@seanlaii
Copy link
Contributor Author

@win5923 Thanks for the review!
@JesseStutler I have updated the doc and added the Chinese version. Please take a look when you have a chance. Thanks!

@JesseStutler
Copy link
Member

/approve
/lgtm
Thanks for your effort!

@volcano-sh-bot volcano-sh-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 25, 2025
@volcano-sh-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JesseStutler, win5923

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@volcano-sh-bot volcano-sh-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 25, 2025
@volcano-sh-bot volcano-sh-bot merged commit 7e0416c into volcano-sh:master Dec 25, 2025
6 checks passed
@seanlaii seanlaii deleted the kuberay-eco branch December 25, 2025 20:45
# Add menu entry to sidebar.
linktitle = "Ray"
[menu.docs]
parent = "ecosystem"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find the zh doc in the website, I saw that the parent in other zh docs under "生态" is called "zoology", which is very weird, could you help us fix it and submit a new PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, will send a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants