Kubecost Data Audit
Last updated
Last updated
When configuring the Cloud Billing Integration, Kubecost is able to reconcile its predictions (which leverage public pricing APIs) with actual billing data to improve accuracy. After Kubecost ingests and reconciles against your cloud billing data, it's able to provide 95%+ accuracy for Kubernetes costs, and 99%+ accuracy for out-of-cluster costs.
This doc provides guidance on how to validate the prices in Kubecost match that of your cloud provider's cost management dashboard.
Before comparing costs between Kubecost and your cloud provider's cost management dashboard, ensure your Kubecost deployment has configured Cloud Billing Integrations.
Auditing Kubecost data is most effective when targeting small ranges of time. In this doc, the primary goal is to ensure the price of a single node for a single day is correct. Then, there is more confidence when comparing with a window of 7 days. Or when comparing cost of the entire cluster. Or when aggregating costs by account or label.
Also, keep in mind that it typically takes ~24-48hrs for cloud providers to provide new billing data, then for Kubecost to ingest this new data and reconcile its predictions against the billing data.
Go to the Assets page, then select Aggregate By > Single Aggregation > Service.
Audits are most effective when targeting small ranges of time. Select a Start and End Date which covers a window of 1 day, and is beyond 48 hours ago. Also select a date that has reconciled with the AWS Cost and Usage Report (CUR). CUR data can be delayed up to 24 hours.
Select the Kubernetes service from the table underneath the NAME column, then select Node. You should arrive at a page like this (if your information is displayed in a bar graph, you can change the display by selecting Edit, then Entire Window under the Resolution dropdown):
Select any node to view its details.
For more configuration options, visit the Assets API doc.
