Kubernetes provisioning

Kubernetes deployment packages every rendered dashboard as a ConfigMap discovered by the Grafana dashboard sidecar.

When to use

Use this page to understand the generated dashboard, its panels, and the signals behind them.

Behavior

Dashboard JSON is rendered before deployment and converted to ConfigMaps. Service identity labels are normalized so the same dashboard definitions work in Compose and Kubernetes.

Provisioning contract properties

Panels included in this dashboard.

PropertyTypeDescription

Dashboard ConfigMapPanel

Every generated dashboard JSON file is stored in a dedicated ConfigMap.

`grafana_dashboard=1`Panel

Label used by the Grafana sidecar to discover dashboard ConfigMaps.

`servicegen.dev/generated-dashboard=true`Panel

Identifies resources owned by generated dashboard provisioning.

`grafana_folder=<service-name>`Panel

Annotation that places the dashboard in the Grafana folder derived from the designer service name.

Observability stackPanel

The deployment installs Grafana and Prometheus through kube-prometheus-stack and also provisions Loki, Jaeger, and the OpenTelemetry Collector used by generated services.

Configuration example

make grafana-dashboards
make kubernetes-up