Skip to content
New issue

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

[RayService] Remove WaitForServeDeploymentReady #2842

Merged

Conversation

kevin85421
Copy link
Member

@kevin85421 kevin85421 commented Jan 28, 2025

Why are these changes needed?

For KubeRay v1.3, we decide to introduce conditions for RayService CRD. For ServiceStatus, we only decide to keep Running and empty string. ServiceStatus is equivalent to Ready condition.

Related issue number

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: kaihsun <[email protected]>
@kevin85421 kevin85421 marked this pull request as ready for review January 28, 2025 07:31
@kevin85421 kevin85421 merged commit 17a534d into ray-project:master Jan 28, 2025
24 checks passed
@andrewsykim
Copy link
Collaborator

@kevin85421 @MortalHappiness could we add a description or comments in the PR adding more details for why WaitForServeDeploymentReady is being removed? It seems like a breaking change and we should document why we are justifying the breaking change

@MortalHappiness
Copy link
Member

@kevin85421 @MortalHappiness could we add a description or comments in the PR adding more details for why WaitForServeDeploymentReady is being removed? It seems like a breaking change and we should document why we are justifying the breaking change

+1. cc @kevin85421

owenowenisme pushed a commit to owenowenisme/kuberay that referenced this pull request Jan 29, 2025
@kevin85421
Copy link
Member Author

Added

@kevin85421 kevin85421 mentioned this pull request Jan 30, 2025
48 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants