Hands-on Lab·Kubernetes and Cloud Native Associate
Grafana Dashboards for Kubernetes
The chart ships Grafana already pointed at Prometheus, with 29 dashboards delivered as ConfigMaps and loaded by a sidecar. Knowing that mechanism is how you add your own - and why editing one in the UI does not last.
Observability Guide 40 of 46 Beginner
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 13 min
Alert names come from kube-prometheus-stack and change between chart versions. The counts are from this cluster.
- Chartkube-prometheus-stack 88.5.3
- Prometheus Operatorv0.93.1
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
This guide includes
Use this when Grafana is installed and you need to know where its dashboards came from and how to add one. This matters because the chart delivers dashboards as ConfigMaps, so adding one is a Kubernetes operation rather than a click in the UI.
- reaching Grafana on its ClusterIP Service from inside the cluster
- reading the admin credentials back out of the chart's Secret
- listing the ConfigMaps labelled
grafana_dashboard=1that carry each dashboard's JSON
Before you start
- kube-prometheus-stack installed with
grafana.enabled=true, which is the chart default.
-
It is running and reachable in-cluster
-
Dashboards are ConfigMaps