We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
.Status.State
rayv1.Ready
Here, as stated in the design doc, we redefine ready as follows:
This new definition is effective only when the RayClusterStatusConditions feature gate is enabled to maintain backward compatibility.
No response
ray-project/enhancements#54 #2219
The text was updated successfully, but these errors were encountered:
Hi @Yicheng-Lu-llll, would you like to take on this?
Sorry, something went wrong.
sure!
Closed by #2271
rueian
Yicheng-Lu-llll
No branches or pull requests
Search before asking
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 torayv1.Ready
, it keepsrayv1.Ready
even when the Head pod is gone.Here, as stated in the design doc, we redefine ready as follows:
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?
The text was updated successfully, but these errors were encountered: