Kubecost Release Process
A Kubecost Release is a snapshot of the source, build output, artifacts, and other metadata associated with a tagged version of code.
- Production releases are scheduled for the first Tuesday of every month.
- Patch releases are pushed as needed between scheduled releases.
- Production releases are always generated from Master branches.
- In each production release, we update each image version plus our helm chart version in lock step.
- Historically we average one patch release between minor releases.
- You can target an older release of the Kubecost pod by setting
imageVersionto the desired value, e.g.
- Release candidates are produced between production releases for early testing
- To pick up a release candidate, add
--develto your helm install/upgrade instructions. For example:
helm install kubecost kubecost/cost-analyzer --namespace kubecost --devel
A Helm chart release is created every night with the latest images. These images should be considered "bleeding edge" and may be unstable. You can get that Helm repo with the following:
helm repo add kubecost-nightly https://kubecost.github.io/nightly-helm-chart
You can then update your existing installation to the latest nightly:
helm repo update
helm upgrade kubecost -n kubecost kubecost-nightly/cost-analyzer
If you want to change your installation back to a production release, run the following (assuming you have a Helm repo called
kubecosttracking the production release):
helm upgrade kubecost kubecost/cost-analyzer -n kubecost
- If you installed our helm chart, all issues can be filed at https://github.com/kubecost/cost-analyzer-helm-chart
- If you installed just the open source cost-model, you can file issues at https://github.com/kubecost/cost-model