[RayService] Refactor to Rely More on RayService Status in RayService E2E Tests #1928
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?
After this PR:
RayServiceAddCREvent
usesserviceStatus
andnumServeEndpoints
to check if it has converged. This addresses the issue described here: [RayService][HA] Fix flaky tests #1823 (comment). CheckingserviceStatus
ensures serve applications within the RayCluster are prepared to handle incoming traffic, and verifyingnumServeEndpoints > 0
confirms that the k8s serve service is ready to redirect traffic to the RayCluster.RayServiceUpdateCREvent
also usesserviceStatus
andnumServeEndpoints
to check if it has converged. This addresses the issue described here: Remove Extra Delay for Zero Downtime Rollout Test #1838 asnumServeEndpoints > 0
can potentially indicate whether the serve service is ready to redirect traffic.RayServiceDeleteCREvent
checks for convergence based on the existence of RayService and RayCluster objects. This is similar to how RayJob e2e tests check for deletion.Related issue number
Closes #1838
Checks