This is the v2.9 branch of the Kubecost Helm chart. This release is designed to facilitate seamless upgrades to v3.0. A federated storage configuration is required when installing v2.9.

There are no new features in v2.9 compared to v2.8 other than the addition of a finops-agent container that will begin collecting metrics in preparation for a seamless upgrade to 3.0.

See ./examples for more information on how to use this version.

All agents must run version 2.9 for at least 2 days before upgrading to v3.0.

Of note, the Kubecost 3.0 chart is stored in a different repo than 2.x. To install version 2.9, you will need to use the 2.x legacy chart location.

helm upgrade kubecost -n kubecost \
  --repo https://kubecost.github.io/cost-analyzer/ cost-analyzer
  -f new-2.9x-values.yaml

Kubecost strives to support as many versions of Kubernetes as possible. Below is the version support matrix which has been tested. Versions outside of the stated range may still work but are untested. While the below versions may work with the given versions of Kubernetes, Kubecost generally supports the current and previous version

To install via Helm, run the following command.

helm upgrade --install kubecost -n kubecost --create-namespace \
  --repo https://kubecost.github.io/cost-analyzer/ cost-analyzer \
  --set kubecostToken="aGVsbUBrdWJlY29zdC5jb20=xm343yadf98"

Alternatively, add the Helm repository first and scan for updates.

helm repo add kubecost https://kubecost.github.io/cost-analyzer/
helm repo update

Next, install the chart.

helm install kubecost kubecost/cost-analyzer -n kubecost --create-namespace \
  --set kubecostToken="aGVsbUBrdWJlY29zdC5jb20=xm343yadf98"

While Helm is the recommended install path for Kubecost, especially in production, Kubecost can alternatively be deployed with a single-file manifest using the following command. Keep in mind when choosing this method, Kubecost will be installed from a development branch and may include unreleased changes. We recommend using the manifest from a release branch, such as v1.108.

kubectl apply -f https://raw.githubusercontent.com/kubecost/cost-analyzer-helm-chart/develop/kubecost.yaml

The following table lists commonly used configuration parameters for the Kubecost Helm chart and their default values. Please see the values file for the complete set of definable values.

You can adjust the log output by using the logLevel Helm value and/or the LOG_FORMAT environment variable.

Adjusting the log level increases or decreases the level of verbosity written to the logs. The logLevel property accepts the following values:

• trace
• debug
• info
• warn
• error
• fatal

For example, to set the log level to debug, add the following flag to the Helm command:

--set 'kubecostModel.logLevel=debug'

Adjusting the log format changes the format in which the logs are output making it easier for log aggregators to parse and display logged messages. The LOG_FORMAT environment variable accepts the values JSON, for a structured output, and pretty for a nice, human-readable output.