What this module owns
Kubernetes makes over-provisioning the rational choice for every individual team. Requests are set generously because the cost of being wrong downward is a page and the cost of being wrong upward is invisible. Multiply that by every workload and you get a cluster bill nobody can attribute and nobody feels responsible for. The work of fixing it is not hard, it is just relentless: pull utilization against requests per workload, decide which gaps are real headroom and which are waste, propose new numbers, and get someone to apply them. This module runs that loop continuously — and because it also runs the attribution, the proposal arrives at the team that owns the workload rather than at a platform engineer holding a spreadsheet. Good looks like spend that lands on a named owner, usage-based waste estimates and projected savings attributed to the workload’s owner, and every applied change traceable to the finding that justified it.The workflows inside it
This module contains 3 workflows.Cost allocation
Right-sizing
Pod placement
Nothing in this module mutates production without a human decision: the apply steps are
approve-then-run, and a right-sizing recommendation is graded by a cost-efficiency judge before it
reaches you.
What it needs connected
Enabling it
1
Open Modules → Overview
Kubernetes Cost appears in the Cost Optimization family with the three workflows it contains.
2
Turn it on
Enabling the module adds Kubernetes Cost to your sidebar, with its cost findings list.
3
Connect a cluster and set the autonomy you want
Point the ingest steps at your clusters and billing, then decide whether the apply step opens a
pull request or applies within scope.
What you see when it runs
The module’s sidebar entry lists cost findings. Each one carries the workload it belongs to, the waste estimate behind it, the recommendation with its projected savings, and — once you accept — the change itself, with a link to the pull request where one was opened. Showback reports appear as their own records, so a per-team number has the run that produced it attached rather than being a figure in a slide.Next steps
Cloud Cost
The same loop one layer down, on your cloud vendor bill.
Approvals
How an apply step waits for a human decision.
Evaluations
The judge that grades a cost recommendation.
Agent spend & attribution
What the fleet doing this work costs you.