costgraph-selfhosted chart, which runs CostGraph in your own infrastructure. Helm release notes are on our chart repository; view the index.yaml for the latest published versions.
SLA
- We will provide changelogs for major and minor releases of the chart
- Customers will be made aware of any breaking changes in any release cycle
- Chart versions are independent of the
costgraph-operatorseries, so the numbers do not run continuously
0.2.0 was tagged but never published: the chart repository’s release job was failing at the time, and 0.3.0 superseded it. Its only change, moving vmalert to a shared definition, is part of 0.3.0. Nothing was released between 0.1.0 and 0.3.0.
costgraph-selfhosted v0.3.0
Breaking Changes
-
Every object is renamed and no longer carries the release name. Objects were
<release>-costgraph-selfhosted...; they are nowcostgraph-selfhosted.... The chart is installed once per namespace, so the prefix distinguished nothing, and components rendered by the shared application chart cannot reproduce it. The two StatefulSets,costgraph-selfhosted-postgresandcostgraph-selfhosted-victoria-metrics, are affected. Their PersistentVolumeClaims are not deleted, but the renamed StatefulSets will not claim them and will provision empty volumes instead. If you run the bundled Postgres or the bundled metrics store, take a backup first, then either point the release at the existing volumes or restore into the new ones. If you run your own Postgres and metrics store, which is what we recommend for production, nothing here affects your data. -
Shared values move under
global. A values file using the old paths still parses, and the settings are then ignored, so an install can silently fall back to bundled defaults. Every moved key: -
Per-component resources move under
deployment. Also silent: the old paths parse and are ignored, and the container then runs with no requests or limits.
Updates
- The bundled Redis, vmalert, the aggregator and the ingestion API are rendered from shared chart definitions rather than templates unique to this chart, so they no longer drift from the same components in our own deployment
- vmalert gains a Service per rule set, so
/api/v1/rulescan be reached when a rule is producing no samples. There was no way to reach it before - vmalert reads the recording rules from the aggregator image rather than a ConfigMap built from a copy of them, so the rules cannot fall behind the aggregator that consumes them
- The bundled Redis no longer mounts a service account token
- Configuration changes roll the affected Deployments again: the pods carry a hash of the values that produced them
costgraph-selfhosted v0.1.0
Breaking Changes
- N/A. First release.
Updates
- CostGraph running in your own infrastructure: the API, dashboard, ingestion API, aggregator and vmalert, with Postgres, Redis and a VictoriaMetrics store optionally bundled for evaluation
- Postgres, Redis and the metrics store each take either a URL you provide, a Secret you manage, or a bundled instance. For production we recommend pointing the release at datastores you operate, so cost history outlives a Helm release
- A preflight check runs before an upgrade and reports a database the release cannot use, rather than failing partway through