karmada icon indicating copy to clipboard operation
karmada copied to clipboard

fix(binding): fix needReviseReplicas judgement

Open CharlesQQ opened this issue 1 week ago • 3 comments

What type of PR is this? /kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes https://github.com/karmada-io/karmada/issues/6361

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


CharlesQQ avatar Dec 09 '25 11:12 CharlesQQ

Summary of Changes

Hello @CharlesQQ, I'm Gemini Code Assist[^1]! 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 addresses a bug in the binding controller by refining the logic used to determine when workload replicas need revision. Previously, the system only checked the explicit replica count, potentially missing scenarios where revision was necessary based on more complex workload definitions like resource requirements or component-based replicas. The updated implementation now considers the full ResourceBindingSpec to make this judgment, ensuring more accurate and robust replica management.

Highlights

  • needReviseReplicas Function Update: The needReviseReplicas function in pkg/controllers/binding/common.go has been refactored to accept a *workv1alpha2.ResourceBindingSpec instead of just an int32 replica count.
  • Revised Revision Logic: The logic within needReviseReplicas now correctly determines if replica revision is required by calling bindingSpec.IsWorkload(), providing a more comprehensive check that accounts for various workload definitions.
  • Expanded Test Coverage: The Test_needReviseReplicas in pkg/controllers/binding/common_test.go has been significantly enhanced with new imports and a wide array of test cases to validate the updated function's behavior across different ResourceBindingSpec configurations, including those with replica requirements and multiple components.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

[^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.

gemini-code-assist[bot] avatar Dec 09 '25 11:12 gemini-code-assist[bot]

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

Codecov Report

:x: Patch coverage is 0% with 1 line in your changes missing coverage. Please review. :white_check_mark: Project coverage is 46.61%. Comparing base (7f726b6) to head (45a4940). :warning: Report is 16 commits behind head on master.

Files with missing lines Patch % Lines
pkg/controllers/binding/common.go 0.00% 1 Missing :warning:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7007      +/-   ##
==========================================
- Coverage   46.64%   46.61%   -0.04%     
==========================================
  Files         699      699              
  Lines       48163    48182      +19     
==========================================
- Hits        22465    22459       -6     
- Misses      24002    24027      +25     
  Partials     1696     1696              
Flag Coverage Δ
unittests 46.61% <0.00%> (-0.04%) :arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

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

codecov-commenter avatar Dec 09 '25 11:12 codecov-commenter

/gemini review

RainbowMango avatar Dec 15 '25 09:12 RainbowMango

[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 avatar Dec 15 '25 09:12 karmada-bot

/retest

CharlesQQ avatar Dec 15 '25 10:12 CharlesQQ