Add kustomize images: and configMapGenerator: across services (#264)
## Summary
- Move hardcoded image tags to kustomization.yaml `images:` transformer across **22 services** — image names in manifests become version-agnostic templates, with tags centralized in one place per service
- Replace hand-written ConfigMap manifests with `configMapGenerator:` in **12 services** — config data extracted to standalone files, generated ConfigMaps include content hashes that trigger automatic pod rollouts on changes
- Create new `kustomization.yaml` for **forgejo-runner** and **nvidia-device-plugin** (switches ArgoCD from directory mode to kustomize mode, rendered output identical)
### Services modified
**Images only (8):** cv, devpi, docs, kube-state-metrics, miniflux, navidrome, teslamate, torrent
**Images + configMapGenerator (10):** alloy-k8s, forgejo-runner, frigate, grafana, homepage, kiwix, loki, mosquitto, ntfy, prometheus
**Images only, no configMapGenerator (4):** authentik (skip blueprints — special YAML tags), tailscale-operator-base (Deployment only, CRD image fields left as-is)
**Skipped entirely (6):** argocd (remote upstream), databases (no image fields), external-secrets, grafana-config (cross-kustomization dashboards), immich (Helm-managed), 1password-connect/cloudnative-pg (no kustomization.yaml)
### What changes at deploy time
- **images:** — no functional diff, `kustomize build` produces identical output with tags
- **configMapGenerator:** — ConfigMap names gain hash suffixes (e.g., `prometheus-config` → `prometheus-config-6f42fhctcb`) and all Deployment/StatefulSet/DaemonSet references are updated automatically. Pods will restart once per service on first sync due to the name change
## Test plan
- [x] `kubectl kustomize` builds all 30 service directories successfully
- [x] Image tags verified in rendered output for all modified services
- [x] ConfigMap hash suffixes verified in rendered output
- [x] ConfigMap references in Deployments/StatefulSets confirmed to use hashed names
- [x] All pre-commit hooks pass (yamllint, shellcheck, prettier, etc.)
- [ ] `argocd app diff` each service to confirm only expected ConfigMap name changes
- [ ] Deploy from branch starting with a low-risk service (e.g., mosquitto)
Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/264
2026-02-24 14:25:19 -08:00
|
|
|
apiVersion: 1
|
|
|
|
|
datasources:
|
|
|
|
|
- access: proxy
|
|
|
|
|
editable: false
|
|
|
|
|
isDefault: true
|
|
|
|
|
name: Prometheus
|
|
|
|
|
orgId: 1
|
|
|
|
|
type: prometheus
|
|
|
|
|
uid: prometheus
|
|
|
|
|
url: http://prometheus.monitoring.svc.cluster.local:9090
|
|
|
|
|
- access: proxy
|
|
|
|
|
editable: false
|
|
|
|
|
name: Loki
|
|
|
|
|
orgId: 1
|
|
|
|
|
type: loki
|
|
|
|
|
uid: loki
|
|
|
|
|
url: http://loki.monitoring.svc.cluster.local:3100
|
2026-03-05 10:51:07 -08:00
|
|
|
jsonData:
|
|
|
|
|
derivedFields:
|
|
|
|
|
- datasourceUid: tempo
|
|
|
|
|
matcherRegex: '"traceID":"(\w+)"'
|
|
|
|
|
name: TraceID
|
|
|
|
|
url: "$${__value.raw}"
|
|
|
|
|
- access: proxy
|
|
|
|
|
editable: false
|
|
|
|
|
name: Tempo
|
|
|
|
|
orgId: 1
|
|
|
|
|
type: tempo
|
|
|
|
|
uid: tempo
|
|
|
|
|
url: http://tempo.monitoring.svc.cluster.local:3200
|
|
|
|
|
jsonData:
|
|
|
|
|
tracesToLogsV2:
|
|
|
|
|
datasourceUid: loki
|
|
|
|
|
filterByTraceID: true
|
|
|
|
|
filterBySpanID: false
|
|
|
|
|
tracesToMetrics:
|
|
|
|
|
datasourceUid: prometheus
|
|
|
|
|
spanStartTimeShift: "-1h"
|
|
|
|
|
spanEndTimeShift: "1h"
|
|
|
|
|
queries:
|
|
|
|
|
- name: Request rate
|
|
|
|
|
query: "sum(rate(traces_spanmetrics_calls_total{$$__tags}[5m]))"
|
|
|
|
|
- name: Error rate
|
|
|
|
|
query: "sum(rate(traces_spanmetrics_calls_total{$$__tags, status_code=\"STATUS_CODE_ERROR\"}[5m]))"
|
|
|
|
|
- name: Duration (p95)
|
|
|
|
|
query: "histogram_quantile(0.95, sum(rate(traces_spanmetrics_duration_seconds_bucket{$$__tags}[5m])) by (le))"
|
|
|
|
|
serviceMap:
|
|
|
|
|
datasourceUid: prometheus
|
|
|
|
|
nodeGraph:
|
|
|
|
|
enabled: true
|
Add kustomize images: and configMapGenerator: across services (#264)
## Summary
- Move hardcoded image tags to kustomization.yaml `images:` transformer across **22 services** — image names in manifests become version-agnostic templates, with tags centralized in one place per service
- Replace hand-written ConfigMap manifests with `configMapGenerator:` in **12 services** — config data extracted to standalone files, generated ConfigMaps include content hashes that trigger automatic pod rollouts on changes
- Create new `kustomization.yaml` for **forgejo-runner** and **nvidia-device-plugin** (switches ArgoCD from directory mode to kustomize mode, rendered output identical)
### Services modified
**Images only (8):** cv, devpi, docs, kube-state-metrics, miniflux, navidrome, teslamate, torrent
**Images + configMapGenerator (10):** alloy-k8s, forgejo-runner, frigate, grafana, homepage, kiwix, loki, mosquitto, ntfy, prometheus
**Images only, no configMapGenerator (4):** authentik (skip blueprints — special YAML tags), tailscale-operator-base (Deployment only, CRD image fields left as-is)
**Skipped entirely (6):** argocd (remote upstream), databases (no image fields), external-secrets, grafana-config (cross-kustomization dashboards), immich (Helm-managed), 1password-connect/cloudnative-pg (no kustomization.yaml)
### What changes at deploy time
- **images:** — no functional diff, `kustomize build` produces identical output with tags
- **configMapGenerator:** — ConfigMap names gain hash suffixes (e.g., `prometheus-config` → `prometheus-config-6f42fhctcb`) and all Deployment/StatefulSet/DaemonSet references are updated automatically. Pods will restart once per service on first sync due to the name change
## Test plan
- [x] `kubectl kustomize` builds all 30 service directories successfully
- [x] Image tags verified in rendered output for all modified services
- [x] ConfigMap hash suffixes verified in rendered output
- [x] ConfigMap references in Deployments/StatefulSets confirmed to use hashed names
- [x] All pre-commit hooks pass (yamllint, shellcheck, prettier, etc.)
- [ ] `argocd app diff` each service to confirm only expected ConfigMap name changes
- [ ] Deploy from branch starting with a low-risk service (e.g., mosquitto)
Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/264
2026-02-24 14:25:19 -08:00
|
|
|
- access: proxy
|
|
|
|
|
database: teslamate
|
|
|
|
|
editable: false
|
|
|
|
|
jsonData:
|
|
|
|
|
database: teslamate
|
|
|
|
|
connMaxLifetime: 14400
|
|
|
|
|
maxIdleConns: 2
|
|
|
|
|
maxOpenConns: 5
|
|
|
|
|
sslmode: disable
|
|
|
|
|
name: TeslaMate
|
|
|
|
|
orgId: 1
|
|
|
|
|
secureJsonData:
|
|
|
|
|
password: $TESLAMATE_DB_PASSWORD
|
|
|
|
|
type: postgres
|
|
|
|
|
uid: TeslaMate
|
2026-06-03 12:25:30 -07:00
|
|
|
# teslamate DB migrated to ringtail blumeops-pg (wave-1); reached via the
|
|
|
|
|
# Caddy L4 route on indri (pg.ops.eblu.me:5434 -> blumeops-pg-ringtail).
|
|
|
|
|
url: pg.ops.eblu.me:5434
|
Add kustomize images: and configMapGenerator: across services (#264)
## Summary
- Move hardcoded image tags to kustomization.yaml `images:` transformer across **22 services** — image names in manifests become version-agnostic templates, with tags centralized in one place per service
- Replace hand-written ConfigMap manifests with `configMapGenerator:` in **12 services** — config data extracted to standalone files, generated ConfigMaps include content hashes that trigger automatic pod rollouts on changes
- Create new `kustomization.yaml` for **forgejo-runner** and **nvidia-device-plugin** (switches ArgoCD from directory mode to kustomize mode, rendered output identical)
### Services modified
**Images only (8):** cv, devpi, docs, kube-state-metrics, miniflux, navidrome, teslamate, torrent
**Images + configMapGenerator (10):** alloy-k8s, forgejo-runner, frigate, grafana, homepage, kiwix, loki, mosquitto, ntfy, prometheus
**Images only, no configMapGenerator (4):** authentik (skip blueprints — special YAML tags), tailscale-operator-base (Deployment only, CRD image fields left as-is)
**Skipped entirely (6):** argocd (remote upstream), databases (no image fields), external-secrets, grafana-config (cross-kustomization dashboards), immich (Helm-managed), 1password-connect/cloudnative-pg (no kustomization.yaml)
### What changes at deploy time
- **images:** — no functional diff, `kustomize build` produces identical output with tags
- **configMapGenerator:** — ConfigMap names gain hash suffixes (e.g., `prometheus-config` → `prometheus-config-6f42fhctcb`) and all Deployment/StatefulSet/DaemonSet references are updated automatically. Pods will restart once per service on first sync due to the name change
## Test plan
- [x] `kubectl kustomize` builds all 30 service directories successfully
- [x] Image tags verified in rendered output for all modified services
- [x] ConfigMap hash suffixes verified in rendered output
- [x] ConfigMap references in Deployments/StatefulSets confirmed to use hashed names
- [x] All pre-commit hooks pass (yamllint, shellcheck, prettier, etc.)
- [ ] `argocd app diff` each service to confirm only expected ConfigMap name changes
- [ ] Deploy from branch starting with a low-risk service (e.g., mosquitto)
Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/264
2026-02-24 14:25:19 -08:00
|
|
|
user: teslamate
|