feat: Add runtimeClassName support for head and worker Pods #4184
Conversation
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
win5923
reviewed
Nov 10, 2025
Collaborator
|
Could you also install pre-commit to fix linting errors? |
win5923
reviewed
Nov 10, 2025
Collaborator
|
Hi @Narwhal-fish, Could you rebase onto the main branch? We’ve just fixed the CI. |
Narwhal-fish
force-pushed
the
Support-runtimeClassName-in-values-yaml
branch
from
5277471 to
f864b30
Compare
Author
Sure! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why are these changes needed?
The ray-cluster Helm chart currently does not support setting runtimeClassName for Ray pods. This field is required when running Ray clusters with GPU runtimes.
This PR adds support for specifying runtimeClassName directly in the ymal file.
Related issue number
#3793
Checks