[Bug][RayService] KubeRay does not recreate Serve applications if a head Pod without GCS FT recovers from a failure. #1420
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 function
checkIfNeedSubmitServeDeployment
is used to determine whether to update or create Ray Serve applications. Without this PR, this function returns true in the following two conditions:(1) When there is no Serve config cache in the KubeRay operator, indicating that either a new RayCluster has just become ready or the KubeRay operator has crashed.
(2) When the Serve config in the cache differs from the RayService CR's ServeConfigV2, indicating an in-place Serve config update.
However, in the case of a head Pod crash and restart without GCS FT, the KubeRay operator will not send a request to create new Ray Serve applications because the Serve config cache remains the same as the RayService CR's ServeConfigV2.
Furthermore, the RayCluster will not be labeled as unhealthy because the function
getAndCheckServeStatus
does not handle the edge case when the number of Ray Serve applications is 0.TODO
e2e test
Related issue number
Checks
Without this PR, you cannot see any Serve application in Step 6.