Kubecost Pod Missing Pricing Metrics
criticalconfigurationUpdated Feb 23, 2026
When Kubecost cannot load or verify node pricing metrics (node_cpu_hourly_cost, node_ram_hourly_cost), cost allocation becomes inaccurate or fails entirely, leading to incomplete cost visibility.
How to detect:
Query Prometheus for node_cpu_hourly_cost, node_ram_hourly_cost, node_total_hourly_cost, and pv_hourly_cost metrics. If these metrics are missing or return no data, Kubecost cannot accurately allocate costs.
Recommended action:
Verify Kubecost is properly scraping metrics from Prometheus. Check that the Prometheus scrape target for Kubecost is configured correctly. Ensure custom pricing configurations are properly applied and that cloud provider integration (if used) is functional.