fix(fuzeagent): raise namespace CPU-limit quota 4->6 for a2a-shared go-live - #115
Merged
Conversation
…o-live fuzeagent-quota capped limits.cpu at 4 and it was fully consumed by the existing workloads, so a2a-shared (limits.cpu=500m) could not schedule: FailedCreate: exceeded quota: fuzeagent-quota ... limited: limits.cpu=4 Only the CPU-limit ceiling was tight (memory 4/8Gi, pods 8/20, requests 450m/2 all had headroom). 6 fits a2a plus its rolling-update surge; limits are ceilings, not reservations (requests.cpu cap stays 2). Unblocks the #93 A2A prod bring-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session-Id: 17fb89fd-3579-433b-a6c4-9c9e7f3ec549
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
1 participant
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.
a2a-shared(from #93) can't schedule —fuzeagent-quotacapslimits.cpuat 4 and it's fully used by existing pods (FailedCreate: exceeded quota ... limited: limits.cpu=4). Only the CPU-limit ceiling is tight (memory 4/8Gi, pods 8/20, requests 450m/2 have headroom). BumpsresourceGovernance.quota.limitsCpu4→6 (fits a2a's 500m + its rolling-update surge; limits are ceilings, requests.cpu cap unchanged at 2). Argo (fuzeagent app) syncs → the pending a2a-shared pod schedules.🤖 Generated with Claude Code