A cluster’s infrastructure bill does not immediately tell you which application or team caused the cost. OpenCost combines Kubernetes resource information with pricing to estimate how that spending is distributed across workloads and organizational groupings. It helps teams investigate expensive services and discuss budgets using a common allocation model. These are attributed costs, so shared resources, discounts and pricing assumptions affect the result; an allocation report is not necessarily an exact reproduction of the provider’s invoice.
Chart ownership
The OpenCost project publishes the opencost chart through https://opencost.github.io/opencost-helm-chart. Its installation guidance recommends Helm for the full configuration surface and distinguishes project-supported installation from third-party convenience installers.
Before adoption
Identify the Prometheus data source, required metrics and history retention. Review cloud-provider credentials and the pricing configuration for your environment. Validate allocations against known workloads and relevant billing data before using them for internal chargeback. Discounts, shared resources and missing labels can affect interpretation. Restrict access to cost and usage information where team or workload names are sensitive, and plan how upgrades preserve the underlying metric history.
Use the installation guidance and project chart source to select the correct provider configuration.
Sources & further reading
Spotted something that needs another look?
Help improve this page →