-
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
Improve logging of workload status #2062
Improve logging of workload status #2062
Conversation
/assign @tenzen-y @alculquicondor |
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -660,9 +661,12 @@ func workloadStatus(w *kueue.Workload) string { | |||
if apimeta.IsStatusConditionTrue(w.Status.Conditions, kueue.WorkloadFinished) { | |||
return finished | |||
} | |||
if workload.HasQuotaReservation(w) { | |||
if workload.IsAdmitted(w) { |
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 really need this distinction? Can we just track quotaReserved
?
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.
Yeah, I was thinking about it, and chose this approach because:
- just renaming to
quotaReserved
would mean we still have misleading logs, but the other way round - having more granular status might be helpful, for example here we only need to enter for admitted
I guess if we have too many occurences of (quotaReserved || admitted)
then we could wrap them with quotaReservedOrAdmitted
helper function.
/lgtm |
LGTM label has been added. Git tree hash: c934797e4eef381f19a2cdd7e80503da19e82b27
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, mimowo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@alculquicondor @tenzen-y should we cherry-pick this? On one hand this is just logs, but OTOH it could be helpful to investigate workloads using ProvReq on 0.6.3. WDYT? |
Considering this conflict (#2061 (comment)), I'd like to vote to cherry pick this PR. |
sgtm |
/cherry-pick release-0.6 |
@mimowo: new pull request created: #2080 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/test-infra repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently, the log messages suggest that the workload is admitted, only if it has quota reserved.
This is confusing when debugging issues related to admission checks.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?