Sections in this category

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

  • Production releases are scheduled for the 2nd and 4th Tuesday of every month.
  • Patch releases are pushed as needed between scheduled releases.
  • Release notes published here.
  • 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 imageVersion to the desired value, e.g. prod-1.63.1

Release candidate (RC) builds

  • Release candidates are produced between production releases for early testing
  • To pick up a release candidate, add --devel to your helm install/upgrade instructions. For example:
helm install kubecost kubecost/cost-analyzer --namespace kubecost --devel

Staging releases

  • Staging releases are built before scheduled releases and published in this repo.
  • You can get the latest staging build by following the install steps

Nightly releases

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 kubecost tracking the production release):

helm upgrade kubecost kubecost/cost-analyzer -n kubecost

Getting notified when a release is created

Submitting feedback on a release

We always love receiving feedback and feature requests. Please reach out to team@kubecost.com or submit an issue in the respective repo:

Edit this doc on Github