How ClusterCost Uses a Single Go Agent to Track All Your Costs

ClusterCost’s agent is one binary that handles data collection, pricing, and enforcement.

• Metrics ingest: reads pod requests/limits and p95 usage from the metrics API.
• Pricing: loads your price sheet (on-demand, spot, storage, egress) into memory.
• Computation: calculates cost per namespace/service and waste in seconds.
• Guardrails: optional admission webhook for labels, limits, and budget caps.
• Outputs: emits metrics, JSON reports, and PR comments via the CLI.
• Network view: captures egress and cross-AZ bytes so traffic costs sit next to compute.
• Caching: keeps cluster metadata hot so CLI queries return fast without extra infra.

Keeping everything in one process means lower footprint and fewer moving parts to upgrade.***