Kubernetes cost allocation reports and cloud invoices often show different numbers because they answer fundamentally different questions — one tracks resource consumption by workload/namespace, the other reflects actual charges including shared infrastructure, idle capacity, discounts, and provider billing models. This gap erodes confidence in cost reporting across engineering, finance, and leadership. The author built Burn, an open-source Kubernetes FinOps CLI that reconciles Kubernetes resource consumption data (via Prometheus) with cloud billing exports, runs as a single binary without extra infrastructure, and integrates with Slack for accessible cost investigation.
Table of contents
Related136 Impressions