Block ResourcePoolClaim spec mutation after allocation to prevent quota overscheduling#1980
Draft
oliverbaehler with Copilot wants to merge 1 commit into
Draft
Block ResourcePoolClaim spec mutation after allocation to prevent quota overscheduling#1980oliverbaehler with Copilot wants to merge 1 commit into
oliverbaehler with Copilot wants to merge 1 commit into
Conversation
Copilot created this pull request from a session on behalf of
oliverbaehler
June 23, 2026 22:03
View session
Collaborator
|
Change makes sense, as Bound is no longer enough to tell if a claim can be mutated. Because Bound can also be |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1980 +/- ##
=======================================
Coverage 11.70% 11.71%
=======================================
Files 362 362
Lines 20096 20096
=======================================
+ Hits 2353 2355 +2
+ Misses 17665 17664 -1
+ Partials 78 77 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
ResourcePool claims could be resized after allocation when
Bound=falsebutstatus.poolwas still set, allowing total claimed quota to exceed pool limits. This change tightens update validation to treat allocation state (not bound-state alone) as immutable for claim spec.Admission guard: allocation-aware immutability
ResourcePoolClaimupdate validation to deny changes tospec.poolandspec.claimwhenever the claim is already allocated to a pool (status.pool.uid != "").E2E behavior: assert denied mutations while allocated
pool_resourcepoolclaim_testexpectations so allocated-but-unused claims cannot: