kodebeat / papers / platform
Turning Kubernetes usage data into a merged requests change
A rightsizing report that emits committable patch YAML.
Reads per-container CPU and memory from kubectl top, a PromQL p95 or VPA targets, compares them against declared requests, applies a published headroom model, and renders a table or patch YAML ready to commit. Sidecars opt out through annotations, so a vendor's container is never rewritten by a script. The gap it fills is the last mile between the dashboard says 180m and a merged pull request.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the Platform & SRE theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.