optimization: replace .Update() with .Patch() for claim updateStatus#508
optimization: replace .Update() with .Patch() for claim updateStatus#508vicentefb wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
✅ Deploy Preview for agent-sandbox canceled.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vicentefb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Let's have the "are there two controllers acting on the same object" discussion on #509 |
2909e6b to
203902d
Compare
|
I ran two very small tests by having 1 claim with a warmpool of size 2. From oss main: Using Update: It tries to update the status at Also something to note is that there's a pod collision in
With this PR: Using Patch: It fires four separate status updates to two different sandboxes (
|
In an effort to reduce "Operation cannot be fulfilled..." conflicts at scale, this PR switches to patching to the status of Sandbox Claim resrouce status.
Tests from main without this change indicate:
322 operation cannot be fulfilled conflicts from sandboxclaim (protoPayload.resourceName="pods/sandboxclaim-" OR protoPayload.resourceName="sandboxclaims/")
With this change, 0 conflicts.
Test paramters:
Deployment args