Repository navigation
Stop replica defaulting loop from blocking suspension propagation - #499
Merged
Merged
Conversation
ecv
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The suspension E2E run showed the annotation on the Karmada WorkloadDeployment but not on the cell after 90 seconds. The cell initializes an unset replica target, while the Karmada desired copy leaves it unset. Repeated cell updates and Work resource-version conflicts prevented the updated annotation from reaching the cell.
Related PR
Verification
go test ./internal/controller -run TestUpsertDownstreamDeploymentReplicaTarget -count=1