[Fix] Add gcsReadyOptions to override wait-gcs-ready init container resources - #5072
Open
aabrower wants to merge 1 commit into
Open
[Fix] Add gcsReadyOptions to override wait-gcs-ready init container resources#5072aabrower wants to merge 1 commit into
aabrower wants to merge 1 commit into
Conversation
…er resources The KubeRay-injected "wait-gcs-ready" init container has hard-coded resources (200m CPU / 256Mi memory). For large Ray images (e.g. bazelized containers), `ray health-check` needs more than 256Mi to run and the init container is repeatedly OOMKilled, wedging worker pods in PodInitializing. Add an optional `spec.gcsReadyOptions.resources` field to RayCluster that overrides the injected init container's resource requests/limits, mirroring the existing `autoscalerOptions.resources` pattern (default values are kept when unset).
aabrower
changed the title
aabrower
marked this pull request as ready for review
August 3, 2026 18:30
aabrower
requested review from
MortalHappiness,
andrewsykim,
kevin85421 and
rueian
as code owners
August 3, 2026 18:30
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
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.
The KubeRay-injected "wait-gcs-ready" init container has hard-coded resources (200m CPU / 256Mi memory). With these resources requests, we are seeing the init container repeatedly OOMKilled
Add an optional
spec.gcsReadyOptions.resourcesfield to RayCluster that overrides the injected init container's resource requests/limits while leaving the defaults unchangedWhy are these changes needed?
Related issue number
#2735
Labels
doc-updates-requiredlabel.breaking-changelabel.Checks
Manual test instructions