Skip to content
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

fix: ResourceBinding to be FullyApplied only when Work Status items are considered Healthy #5868

Closed
wants to merge 1 commit into from

Conversation

a7i
Copy link
Contributor

@a7i a7i commented Nov 24, 2024

What type of PR is this?
/king bug

What this PR does / why we need it:
Fixes ResouceBinding claiming to be fully applied before work status items are evaluated as Healthy

Which issue(s) this PR fixes:
Fixes #5867

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@karmada-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xishanyongye-chang for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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 size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 24, 2024
…tems are considered `Healthy`

Signed-off-by: Amir Alavi <[email protected]>
@@ -283,6 +283,10 @@ func worksFullyApplied(aggregatedStatuses []workv1alpha2.AggregatedStatusItem, t
return false
}

if aggregatedStatusItem.Health != workv1alpha2.ResourceHealthy {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we have 2 member clusters, and it's healthy for one and not the other. Should be it considered fully applied? or not applied?

@a7i
Copy link
Contributor Author

a7i commented Nov 25, 2024

Per discussion in the issue, my use-case will be solved by querying both Health and FullyApplied==True

@a7i a7i closed this Nov 25, 2024
@a7i a7i deleted the fix-rb-fullyapplied branch November 25, 2024 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

ResourceBinding claims FullyApplied when not healthy
2 participants