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.
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
[Feature][RayCluster]: introduce RayClusterSuspending and RayClusterSuspended conditions #2403
[Feature][RayCluster]: introduce RayClusterSuspending and RayClusterSuspended conditions #2403
Changes from 3 commits
8efab0c
ee39d7e
f7fe429
eb9dcf8
7bd5968
e05ff34
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to send a
deleteAllPods
request to the K8s API server for each reconciliation duringSuspending
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we do that until all pods are deleted and then we switch to
suspended
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it complex to call
deleteAllPods
only when there are running Pods in the cluster? If not, we can update in this PR. If it is not trivial, can you open an issue to track the progress?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After revising the source, I found that
deleteAllPods
already did the improvement: only sends API requests if there are Pods still running.kuberay/ray-operator/controllers/ray/raycluster_controller.go
Lines 195 to 210 in 35e913a
I guess there is no need for an issue to track the progress?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we separate the atomicity test into its own test? I want to avoid mixing both code paths in a single test. In the atomicity test, can you verify the following:
suspend
to true, and check that thesuspending
condition is true.suspend
back to false, and ensure thesuspending
condition remains true for 2 to 3 seconds (useConsistently
).suspending
andsuspended
conditions become false, all old Pods are deleted, and new Pods are created.suspend
to true, and all Pods should be deleted.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, a new test is added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explicitly add comments to describe which fields should be updated when the status transitions?