Skip to content

Update logging format for federated resource quota #6592

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

Conversation

zzklachlan
Copy link
Contributor

What type of PR is this?

JSON logging support. More details are highlighted in #6230.

Which issue(s) this PR fixes:

Fixes #
Part of #6230

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

None

@karmada-bot karmada-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 1, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @zzklachlan, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the logging format within the federated resource quota controllers to support structured JSON logging. The change involves refactoring existing klog calls to use InfoS and ErrorS methods, which accept key-value pairs for better log context and machine readability. This enhancement aims to improve the overall observability and debugging experience for the federated resource quota components.

Highlights

  • Structured Logging Adoption: The primary change across the affected files is the migration from traditional klog.Infof and klog.Errorf calls to their structured counterparts, klog.InfoS and klog.ErrorS. This enables logs to be output in a machine-readable, key-value pair format, improving parseability and analysis.
  • Enhanced Error Context: Error logging has been significantly improved by passing the error object directly to klog.ErrorS and including relevant contextual information as explicit key-value pairs (e.g., namespacedName, federatedResourceQuota, workNamespace, object). This makes it easier to understand the context of an error without needing to parse complex string messages.
  • Code Consistency: This update standardizes the logging practices within the federatedresourcequota controllers, aligning them with modern structured logging conventions and promoting better maintainability and observability across the codebase.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors logging statements across the federated resource quota controllers to use structured logging (klog.InfoS/ErrorS) instead of formatted string logging (Infof/Errorf). This is a great improvement for log parsing and analysis.

@codecov-commenter
Copy link

codecov-commenter commented Aug 1, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 7.40741% with 25 lines in your changes missing coverage. Please review.
✅ Project coverage is 45.34%. Comparing base (b8f6874) to head (4f8892d).
⚠️ Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
...equota/federated_resource_quota_sync_controller.go 0.00% 12 Missing ⚠️
...federated_resource_quota_enforcement_controller.go 0.00% 9 Missing ⚠️
...uota/federated_resource_quota_status_controller.go 33.33% 4 Missing ⚠️
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6592   +/-   ##
=======================================
  Coverage   45.34%   45.34%           
=======================================
  Files         687      687           
  Lines       56393    56383   -10     
=======================================
- Hits        25571    25568    -3     
+ Misses      29226    29218    -8     
- Partials     1596     1597    +1     
Flag Coverage Δ
unittests 45.34% <7.40%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

@RainbowMango RainbowMango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good to me.
Would you mind squash the commits?

@jabellard
Copy link
Member

/assign

Signed-off-by: Kai Zhang <[email protected]>

Address gemini code review

Signed-off-by: Kai Zhang <[email protected]>
@zzklachlan zzklachlan force-pushed the json-logging-federated-resource-quota branch from 46899c7 to 4f8892d Compare August 4, 2025 14:11
@zzklachlan
Copy link
Contributor Author

@RainbowMango Just squashed all commits. Appreciate it for the review!

Copy link
Member

@RainbowMango RainbowMango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
Thanks.

@karmada-bot karmada-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2025
@karmada-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@karmada-bot karmada-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2025
@karmada-bot karmada-bot merged commit 140f745 into karmada-io:master Aug 4, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants