REP: Deterministic Label-Based Scheduling with Ray Autoscaler and KubeRay - #68
Open
ryanaoleary wants to merge 1 commit into
Open
REP: Deterministic Label-Based Scheduling with Ray Autoscaler and KubeRay#68ryanaoleary wants to merge 1 commit into
ryanaoleary wants to merge 1 commit into
Conversation
Signed-off-by: Ryan O'Leary <ryanaoleary@google.com>
Contributor
Author
|
cc: @andrewsykim |
ryanaoleary
marked this pull request as ready for review
July 8, 2026 23:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This REP proposes an enhancement to the Ray V2 Autoscaler and KubeRay to support deterministic label-based scheduling.
Currently, Ray autoscaling with label constraints requires pre-configuring multiple
workerGroupSpecscontaining specificnodeSelectorsandrayStartParams. This proposal outlines a solution to enable the Ray V2 Autoscaler to dynamically generateSchedulingNodecandidates based on incoming resource demands with Kubernetes topology label selectors (like region, zone, or market type), and automatically patch theRayClusterCR with temporary, dynamically generatedworkerGroupSpecs.Related doc with some discussion: Deterministic Label-Based Scheduling with Ray Autoscaler and KubeRay