Rightsizing remediation: patch-requests (FEAT-1) - #32
Merged
Conversation
Closes the loop the resource-usage probe opens: when a pod runs hot against its declared requests, `patch-requests` raises (or lowers) them via `kubectl set resources deployment/<name> --requests=cpu=...,memory=...` (optional -c container). It is marked destructive -- it mutates the workload spec and triggers a rolling restart -- so autonomy `auto` is rejected at policy load and a human or the AI approver always gates it. At least one of cpu/memory is required.
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.
Closes the loop the
resource-usageprobe opens (it flags hot pods read-only). The newpatch-requestsremediation raises/lowers a deployment's requests viakubectl set resources deployment/<name> --requests=cpu=...,memory=...(optional-c container).Marked destructive (mutates the spec + triggers a rolling restart), so
autois rejected at policy load — a human or the AI approver always gates it. Requires at least one ofcpu/memory.Registered in
REMEDIATIONS. Tests: command construction (both/cpu-only), the require-a-resource guard, destructive+auto rejection, gated build. 220 passed; ruff/mypy clean. Task #19.