Grafana Configuration Guide
Using an existing Grafana deployment can be accomplished through one of two options:
Linking to an external Grafana directly
Deploying with Grafana sidecar enabled
Option 1: Directly link to an external Grafana
After installing Kubecost, select Settings from the left navigation and update Grafana Address to a URL that is visible to users accessing Grafana dashboards. This variable can alternatively be passed at the time you deploy Kubecost via the kubecostProductConfigs.grafanaURL
parameter in values.yaml. Next, import Kubecost Grafana dashboards as JSON from this folder.
Option 2: Deploy with Grafana sidecar enabled
Passing the Grafana parameters below in your values.yaml will install ConfigMaps for Grafana dashboards that will be picked up by the Grafana sidecar if you have Grafana with the dashboard sidecar already installed.
Ensure that the following flags are set in your Operator deployment:
sidecar.dashboards.enabled=true
sidecar.dashboards.searchNamespace
isn't restrictive. UseALL
if Kubecost runs in another namespace.
The Kubecost UI cannot link to the Grafana dashboards unless kubecostProductConfigs.grafanaURL
is set, either via the Helm chart, or via the Settings page, as described in Option 1.
When using Kubecost on a custom ingress path, you must add this path to the Grafana root_url
:
Disabling Grafana
If you choose to disable Grafana, set the following Helm values to ensure successful pod startup:
Last updated