OpenCost
v1.120.0ObservabilityOpenCost v1.120.0 adds OVH cloud provider support, AWS CUR 2.0 compatibility, and fixes several resource leaks and bugs across AWS, DigitalOcean, and S3 integrations.
enhancementMigrate to AWS CUR 2.0 if you haven't already
AWS is deprecating CUR 1.0 — this release adds CUR 2.0 support. If you're still on CUR 1.0 exports, now is the time to update your AWS billing export configuration and point OpenCost at the new format. Don't wait for AWS to force the migration.
breakingCheck PV cost accuracy after upgrading — unit parsing was broken
PV capacity was previously mishandled for Ki/Mi/Gi/Ti units, which means PV cost allocations may have been wrong in earlier versions. After upgrading, verify your PV cost data looks correct, especially if you were seeing anomalous persistent volume costs.
enhancementSuppress noisy Spot feed warnings with the new toggle
Teams not using AWS Spot instances were getting misleading log warnings about spot data feeds. You can now explicitly disable the Spot Data Feed via config. Set the toggle if you're not using Spot — it cleans up your logs and removes the misleading provider log noise fixed in this release.
Key changes (7)
- New OVH cloud provider integration for cost tracking
- AWS CUR 2.0 (Cost and Usage Report) support added
- Memory leak fixed in Prometheus scrape target parsing
- Plugin processes now properly killed on ingestor shutdown, preventing zombie processes
- PV capacity parsing fixed to correctly handle Ki, Mi, Gi, and Ti units
- Account field added to allocation data, cluster name added to CSV exports
- Configuration toggle added to disable AWS Spot Data Feed when not in use