[RayJob][Status][15/n] Unify the codepath for the status transition to Suspended
#1805
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?
Currently, there are two paths to transition to the
Suspended
status.Initializing
->Suspended
Running
->Suspending
->Suspended
The case "Initializing -> Suspended" is pretty tricky:
suspend
to true before creating the RayCluster.Suspended
directly.suspend
to true after the RayCluster is created and before the K8s Job creation.Running
and then toSuspending
. Additionally, the user must wait until both the RayCluster and the Kubernetes Job are ready to transition toRunning
, which may take a considerable amount of time (depending on the time of pulling images).This PR unifies the codepath for the status transition to
Suspended
.Initializing
->Suspending
->Suspended
Running
->Suspending
->Suspended
Note
WithStatusSubresource
to the fake client, the functionr.Status().Update(...)
will complain that the RayJob cannot be found.Related issue number
Checks