[Feature] REP 54: Re-define rayv1.Ready

[rueian]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

This is one of the tracking items of the REP: RayCluster status improvement, the step 6 in the design doc: https://docs.google.com/document/d/1bRL0cZa87eCX6SI7gqthN68CgmHaB6l3-vJuIse-BrY

Currently, once the .Status.State has been set to rayv1.Ready, it keeps rayv1.Ready even when the Head pod is gone.

Here, as stated in the design doc, we redefine ready as follows:

• When all Pods in the RayCluster are running for the first time, the RayCluster CR’s Status.State will transition to ready.
• After the RayCluster CR transitions to ready, KubeRay only checks whether the Ray head Pod is ready to determine if the RayCluster is ready.

This new definition is effective only when the RayClusterStatusConditions feature gate is enabled to maintain backward compatibility.

Use case

No response

Related issues

ray-project/enhancements#54
#2219

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[rueian]

Hi @Yicheng-Lu-llll, would you like to take on this?

[Yicheng-Lu-llll]

sure！

[kevin85421]

Closed by #2271