Skip to content

[Docs] add docs for prerunning deadline for Kuberay#61552

Merged
edoakes merged 2 commits intoray-project:masterfrom
machichima:doc-pre-running-deadline
Mar 9, 2026
Merged

[Docs] add docs for prerunning deadline for Kuberay#61552
edoakes merged 2 commits intoray-project:masterfrom
machichima:doc-pre-running-deadline

Conversation

@machichima
Copy link
Copy Markdown
Contributor

@machichima machichima commented Mar 7, 2026

@machichima machichima requested a review from a team as a code owner March 7, 2026 06:29
Copy link
Copy Markdown
Contributor

@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 the new preRunningDeadlineSeconds field in KubeRay. The documentation is added to the RayJob quickstart guide and the kubectl plugin user guide. The changes are clear and accurately describe the new feature. I have one minor suggestion to improve consistency in the documentation style.

Note: Security Review has been skipped due to the limited scope of the PR.

Signed-off-by: machichima <nary12321@gmail.com>
Copy link
Copy Markdown
Member

@Future-Outlier Future-Outlier left a comment

Choose a reason for hiding this comment

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

LGTM, cc @edoakes to merge.

@ray-gardener ray-gardener bot added docs An issue or change related to documentation core Issues that should be addressed in Ray Core community-contribution Contributed by the community labels Mar 7, 2026
* `K8sJobMode`: The KubeRay operator creates a submitter Kubernetes Job to submit the Ray job.
* `HTTPMode`: The KubeRay operator sends a request to the RayCluster to create a Ray job.
* `InteractiveMode`: The KubeRay operator waits for the user to submit a job to the RayCluster. This mode is currently in alpha and the [KubeRay kubectl plugin](kubectl-plugin) relies on it.
* `InteractiveMode`: The KubeRay operator waits for the user to submit a job to the RayCluster. This mode is currently in alpha and the [KubeRay kubectl plugin](kubectl-plugin) relies on it. To avoid RayJobs staying in `Initializing` or `Waiting` for too long, set `preRunningDeadlineSeconds`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* `InteractiveMode`: The KubeRay operator waits for the user to submit a job to the RayCluster. This mode is currently in alpha and the [KubeRay kubectl plugin](kubectl-plugin) relies on it. To avoid RayJobs staying in `Initializing` or `Waiting` for too long, set `preRunningDeadlineSeconds`.
* `InteractiveMode`: The KubeRay operator waits for the user to submit a job to the RayCluster. This mode is currently in alpha and the [KubeRay kubectl plugin](kubectl-plugin) relies on it.

I think we should remove this sentence. The other submissionMode (K8sJobMode, HTTPMode, SidecarMode) only describe the mode itself and don't cross-reference unrelated fields. Also, preRunningDeadlineSeconds applies to all modes, not just InteractiveMode, so calling it out here is misleading. Its own definition in the Automatic resource cleanup section is sufficient.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Sure! updated in 278424d

* `submitterConfig` (Optional): Additional configurations for the submitter Kubernetes Job.
* `backoffLimit` (Optional, added in version 1.2.0): The number of retries before marking the submitter Job as failed. The default value is 2.
* Automatic resource cleanup
* `preRunningDeadlineSeconds` (Optional): Maximum number of seconds a RayJob can remain before reaching `Running`. If the RayJob does not transition to `Running` within this deadline (for example, while in `Initializing` or `Waiting`), the KubeRay operator transitions the `JobDeploymentStatus` to `Failed` with reason `PreRunningDeadlineExceeded`. The default value is 0 (no pre-running deadline is enforced).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* `preRunningDeadlineSeconds` (Optional): Maximum number of seconds a RayJob can remain before reaching `Running`. If the RayJob does not transition to `Running` within this deadline (for example, while in `Initializing` or `Waiting`), the KubeRay operator transitions the `JobDeploymentStatus` to `Failed` with reason `PreRunningDeadlineExceeded`. The default value is 0 (no pre-running deadline is enforced).
* `preRunningDeadlineSeconds` (Optional): If the RayJob doesn't transition the `JobDeploymentStatus` to Running within `preRunningDeadlineSeconds` seconds, the KubeRay operator transitions the `JobDeploymentStatus` to Failed with reason `PreRunningDeadlineExceeded`.

I think the description can follow the same pattern as activeDeadlineSeconds for consistency. WDYT?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated in 278424d

Signed-off-by: machichima <nary12321@gmail.com>
Copy link
Copy Markdown
Member

@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.

Thanks!

@Future-Outlier Future-Outlier added the go add ONLY when ready to merge, run all tests label Mar 8, 2026
@edoakes edoakes merged commit e41236c into ray-project:master Mar 9, 2026
7 checks passed
ParagEkbote pushed a commit to ParagEkbote/ray that referenced this pull request Mar 10, 2026
## Description

We introduce new config field `preRunningDeadlineSeconds` in
ray-project/kuberay#4525. This PR add the
related docs.

## Related issues

Related to ray-project/kuberay#4525

## Additional information

docs link:
-
https://anyscale-ray--61552.com.readthedocs.build/en/61552/cluster/kubernetes/getting-started/rayjob-quick-start.html#rayjob-configuration
-
https://anyscale-ray--61552.com.readthedocs.build/en/61552/cluster/kubernetes/user-guides/kubectl-plugin.html#submit-a-ray-job-without-a-yaml-file

---------

Signed-off-by: machichima <nary12321@gmail.com>
Signed-off-by: Parag Ekbote <thecoolekbote189@gmail.com>
abrarsheikh pushed a commit that referenced this pull request Mar 11, 2026
ryanaoleary pushed a commit to ryanaoleary/ray that referenced this pull request Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contributed by the community core Issues that should be addressed in Ray Core docs An issue or change related to documentation go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants