Setup grafana dashboards - 2i2c Infrastructure Guide

Now, we will deploy some specific dashboards to the grafana instance we deployed as part of Configure and deploy the support chart.

Login to the cluster-specific grafana¶

Eventually, visiting GRAFANA_URL (which we set in Configure and deploy the support chart) will present you with a login page. Here are the credentials for logging in:

username: admin
password: located in helm-charts/support/enc-support.secret.values.yaml (sops encrypted).

Create an API key to auto-deploy the dashboards¶

Once the support chart is deployed and you are able to log into grafana as the admin user, you can generate an API key.

You can do this by running a deployer command:

export CLUSTER_NAME=<cluster-name>

deployer grafana new-token $CLUSTER_NAME

If the command succeeded, it should have created:

a Grafana service account named deployer
a token named deployer for this service account
the following sops-ecrypted file config/clusters/<cluster>/enc-grafana-token.secret.yaml, with a content similar to:
```
grafana_token: token
```

The encrypted file can now be committed to the repository.

Deploying the Grafana Dashboards locally¶

You can deploy the dashboards locally using the deployer:

deployer deploy-dashboards $CLUSTER_NAME

Deploying the Grafana Dashboards from CI/CD¶

Once you’ve pushed the encrypted grafana_token to the GitHub repository, it will be possible to manually trigger the deploy-grafana-dashboards workflow using the “Run workflow” button to deploy the dashboards.

Granting grafana access to the community representative¶

Once you have setup the grafana instance, you may wish to Give Grafana access to a community representative only if the cluster is dedicated to one community.