-
Notifications
You must be signed in to change notification settings - Fork 262
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
Use DeactivationTarget to improve message when deactivating due to Rejected AdmissionChecks #3331
Comments
I see @KPostOffice is already working on this under #3350 |
/assign @KPostOffice |
@mimowo: GitHub didn't allow me to assign the following users: KPostOffice. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@KPostOffice you should be able to assign yourself |
/assign |
What would you like to be added:
When deactivating due to rejected admission checks we just active=false:
kueue/pkg/controller/core/workload_controller.go
Lines 370 to 379 in 3d278a9
Then, the generic message for the
Evicted
condition is set here.The message can be improved when DeactivationTarget is used, see here.
The message candidate:
The workload is deactivated due to rejected AdmissionChecks(s): check1, check2.
Why is this needed:
To inform the end user about the reason of deactivation.
The text was updated successfully, but these errors were encountered: