Preserve CRP scheduled status across non-scheduling spec updates#730
Draft
Simon Waight (sjwaight) with Copilot wants to merge 4 commits into
Draft
Preserve CRP scheduled status across non-scheduling spec updates#730Simon Waight (sjwaight) with Copilot wants to merge 4 commits into
Simon Waight (sjwaight) with Copilot wants to merge 4 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix resetting of ClusterResourcePlacementScheduled condition in CRP spec
Preserve CRP scheduled status across non-scheduling spec updates
May 29, 2026
Member
|
michaelawyu (@michaelawyu) can you please review when you get time. |
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
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.
Updating CRPs at scale with spec changes that do not affect scheduling could reset
ClusterResourcePlacementScheduledtoUnknown, which in turn drove the placement controller into the backup requeue path and inflated workqueue depth. This was most visible on bulk updates such as rollout-strategy changes across thousands of CRPs.Root cause
CRPGenerationAnnotationeven when the scheduling policy itself was unchanged.buildScheduledCondition(), which resetClusterResourcePlacementScheduledtoSchedulePending/Unknown."Scheduler has not scheduled any cluster yet and requeue the request as a backup"path.What changed
ObservedCRPGeneration < placement.Generationas sufficient reason to reset the CRP scheduled condition toUnknown.Behavioral impact
ClusterResourcePlacementScheduledback toUnknown.Targeted coverage
CRPGenerationAnnotationare tolerated in this path.