nils/mg4

Files

T

nilsandClaude Opus 5.5 756ae65d0b Grafana: startup probe so a slow first start is not killed

Grafana's first start creates and migrates its database: 44 s at
0.5 CPU and 3 minutes at 0.1 CPU (measured with 13.2.3 on an empty
volume). With only 50m requested, the liveness probe (30 s delay,
3 x 30 s) restarted it mid-migration, in a loop, and readiness never
passed.

- startupProbe on /api/health allows up to 10 minutes; liveness and
  readiness start only after it succeeds.
- 5 s timeouts on all probes instead of the 1 s default.
- Requests raised to 250m CPU / 256Mi (measured about 240 MB in use);
  still no CPU limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki

2026-10-17 21:43:49 +02:00

grafana

Dashboards in Grafana; clean up after the Next.js app

2026-10-17 15:18:09 +02:00

secrets

k8s: work with kubectl apply -f as well as -k

2026-10-17 21:36:17 +02:00

grafana.yaml

Grafana: startup probe so a slow first start is not killed

2026-10-17 21:43:49 +02:00

influxdb.yaml

Dashboards in Grafana; clean up after the Next.js app

2026-10-17 15:18:09 +02:00

ingress.yaml

k8s: work with kubectl apply -f as well as -k

2026-10-17 21:36:17 +02:00

kustomization.yaml

k8s: work with kubectl apply -f as well as -k

2026-10-17 21:36:17 +02:00

namespace.yaml

Add Kubernetes manifests for car.stinnesbeck.com

2026-10-17 14:11:58 +02:00

README.md

k8s: work with kubectl apply -f as well as -k

2026-10-17 21:36:17 +02:00

server.yaml

k8s: work with kubectl apply -f as well as -k

2026-10-17 21:36:17 +02:00

README.md

Kubernetes manifests — car.k8s.stinnesbeck.com

Plain manifests for the car server, InfluxDB 2 and Grafana. They are only files: nothing here is applied automatically. Apply them yourself.

File	What
`namespace.yaml`	Namespace `mg4`
`influxdb.yaml`	InfluxDB 2.7.12 StatefulSet (10Gi PVC, default storage class), cluster-internal Service, NetworkPolicy admitting only the server and Grafana
`server.yaml`	Go server Deployment (1 replica, non-root, read-only root filesystem) and Service
`grafana.yaml`	Grafana 13.2.3 Deployment (1Gi PVC), Service; datasource and dashboards provisioned
`grafana/`	The provisioned InfluxDB datasource and the MG4 dashboards (Live, Consumption, Charging)
`ingress.yaml`	Traefik `IngressRoute`s for car.k8s.stinnesbeck.com and Grafana, TLS from Traefik's default certificate
`secrets/secrets.example.yaml`	Template for the Secrets; placeholders only, not in `kustomization.yaml`
`secrets/secrets.yaml`	Your filled-in copy — gitignored, never committed
`kustomization.yaml`	Everything except the Secrets; generates the Grafana ConfigMaps

Before the first apply

Check ingress.yaml: Grafana's host (placeholder car-grafana.k8s.stinnesbeck.com). Both routes use the traefik-internal class, and both hosts must be covered by Traefik's default certificate.
Create the Secrets. cp k8s/secrets/secrets.example.yaml k8s/secrets/secrets.yaml (gitignored), replace every CHANGE-ME there (openssl rand -hex 32): influxdb-auth, mg4-server (ingest token, approval password for pairing, your ABRP API key and user token) and grafana-admin. Keep the template itself on placeholders only.
Registry access. The mg4-server package on git.stinnesbeck.com is public, so no pull secret is needed. If you make it private, add an imagePullSecrets entry to server.yaml.

Apply

kubectl apply -f k8s/namespace.yaml
kubectl apply -f k8s/secrets/secrets.yaml
kubectl apply -k k8s/

Use -k, not -f k8s/: plain -f applies the files without kustomize, so the Grafana ConfigMaps (datasource and dashboards) are never created and Grafana does not start.

Notes

InfluxDB's setup mode runs only on an empty volume. Changing admin-token in the Secret later does not change the token inside InfluxDB.
The server and Grafana use the InfluxDB admin token. A token scoped to the mg4 bucket (read for Grafana, read/write for the server) can replace it later.
The dashboards are read-only in Grafana's UI. Change the JSON in grafana/dashboards/; the ConfigMap name changes with its content, which rolls Grafana.
The server image is pinned by digest in server.yaml. To upgrade, push a new tag and put its digest there (skopeo inspect docker://git.stinnesbeck.com/nils/mg4-server:<tag>).