-
Notifications
You must be signed in to change notification settings - Fork 425
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]: Add a new event type FailedToDeleteWorkerPodCollection #2680
base: master
Are you sure you want to change the base?
[Feature]: Add a new event type FailedToDeleteWorkerPodCollection #2680
Conversation
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.
Check all places that use FailedToDeleteWorkerPod
, and change them to FailedToDeleteWorkerPodCollection
if DeleteAllOf
is used instead of Delete
.
Ref: https://github.com/ray-project/kuberay/pull/2663/files#r1893148428
@MortalHappiness I searched for functions related to |
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.
I will review this after #2663 is merged.
e101a6b
to
debd1e1
Compare
@MortalHappiness @kevin85421 I have checked all of the functions related to |
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.
LGTM
Why are these changes needed?
Currently, we are reusing the
FailedToDeleteWorkerPod
event type for scenarios where bothDelete
(requiring thedelete
verb inRole
orClusterRole
) andDeleteAllOf
(requiring thedeletecollection
verb) are involved. However, this reuse may lead to confusion because these operations rely on different verbs and permissions.To improve clarity and maintainability, we should consider introducing a new event type specific to the
DeleteAllOf
operation.Related issue number
Closes #2672
Checks