Skip to content

docs: design for scoping consolidation validation#2

Open
jamesmt-aws wants to merge 2 commits intomainfrom
consolidation-validation-design
Open

docs: design for scoping consolidation validation#2
jamesmt-aws wants to merge 2 commits intomainfrom
consolidation-validation-design

Conversation

@jamesmt-aws
Copy link
Copy Markdown
Owner

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

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>
@jamesmt-aws jamesmt-aws force-pushed the consolidation-validation-design branch from be16a41 to feb94f7 Compare March 10, 2026 03:31
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant