Migrate Helm chart artifacts to grafana/cloudcost-exporter for CD ownership & consistency #743
Description
What?
Migrate the Helm chart artefacts into the grafana/cloudcost-exporter repo by creating a workflow in this repo.
Why?
1. Ownership
When there is a new release of the cloudcost-exporter application, we need 2 reviews for PRs to the grafana/helm-charts repository, which slows down our release process. We have fallen behind on the application version used in the Helm chart. We could fully automate the release and deployment process if the Helm chart artefacts were closer to the application code.
2. Consistency
Having the Helm chart artefacts close to the source code would maintain consistency with the OSS strategy of other grafana/<projects> repositories:
- Alloy
- Alloy Operator - Release workflow (I made this most recently, so it utilizes more of our shared workflows)
- Loki
How?
The workflow should abstract away as many steps as possible by using shared workflows. For example, @petewall shared the Alloy Operator's Helm chart uses this release workflow that references many Grafana Labs shared workflows.