docs: design for scoping consolidation validation#2
Open
jamesmt-aws wants to merge 2 commits intomainfrom
Open
docs: design for scoping consolidation validation#2jamesmt-aws wants to merge 2 commits intomainfrom
jamesmt-aws wants to merge 2 commits intomainfrom
Conversation
3 tasks
472531c to
be16a41
Compare
Consolidation validation operates on global cluster state, so any change to any NodePool can invalidate a plan that only affects one NodePool. This design proposes three scoping changes, one per validation stage, so that only changes relevant to the candidate's own pods and nodes can invalidate a plan. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
be16a41 to
feb94f7
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
Design doc for scoping consolidation validation to candidate-relevant state. Consolidation validation currently operates on global cluster state, so any change to any NodePool can permanently block consolidation of unrelated NodePools.
Proposes three scoping changes, one per validation stage, so that only changes relevant to the candidate's own pods and nodes can invalidate a plan.
Related issues
Implementation
Code changes in a separate PR: consolidation-invalidation-fix
🤖 Generated with Claude Code