Container Cost Attribution in Multi-Tenant Clusters
Multi-tenant clusters save money on infrastructure and lose visibility on per-team spend. Tooling closes the gap.
Why multi-tenant hides cost
Cluster bill is one line item. Per-team spend is computed; the computation is opinionated.
Without the computation, no team owns their fraction.
Four attribution patterns
- 1. Kubecost (commercial; broad adoption).
- 2. OpenCost (CNCF open-source; same data).
- 3. Custom metrics (DIY).
- 4. Label-based attribution (manual).
Tool comparison
Kubecost: easiest to deploy; pay for advanced features.
OpenCost: same core engine; free; ops cost.
Custom: fits unique needs; engineering cost.
Negotiating the math
The math is opinionated, idle capacity, networking, storage attribution all have judgment calls.
Document the model; teams accept the math when they understand it.
Antipatterns
- No attribution. Spend grows uncontrolled.
- Attribution without team buy-in. Argued every quarter.
- Switching tools quarterly. Math discontinuous.
What to do this week
Three moves. (1) Apply this lever to your highest-spend workload. (2) Measure the dollar impact for one month. (3) Roll the practice out to the next two services if the savings hold.