-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
DRA: helper logging improvements #120340
DRA: helper logging improvements #120340
Conversation
Instead of emitting two log entries for new or updated ResourceClaim and PodSchedulingContext, add the additional information for V(6) to the logger via WithValues and emit one log entry. This makes the log shorter and easier to read because related information is on one line.
Here's what it looked like before: err="allocation of one or more pod claims failed. Claim test-dra5z9nh-resource-1an8wcr: failed allocating claim 4739f9a2-eedc-4702-ab17-e201e2dc0ad2. Claim test-dra5z9nh-resource-1bbdsj2: failed allocating claim e5525e5a-3397-40b4-a633-9ac354605303." Some observations: - Inserting the claim UID is just noise because it doesn't get logged anywhere else. - Concatenating on a single line makes it hard to see the individual errors. Joining with errors.Join leads to more readable output. The claim name only gets inserted if not present already, to keep the individual error entries short: err=< claim test-dralmx55-resource-1asvr5d: resources exhausted on node "scheduler-perf-dra-w62wm" claim test-dralmx55-resource-1bqq6c9: resources exhausted on node "scheduler-perf-dra-w62wm" >
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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 |
/triage accepted |
/lgtm |
LGTM label has been added. Git tree hash: b3d861551b6bd7a095a94ff29a7e4f3e051720f0
|
/retest the "OOM killer" flake |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Makes log output easier to read.
Does this PR introduce a user-facing change?