From 76a6213126eb129f86a6ff97387cd85993e09f4d Mon Sep 17 00:00:00 2001 From: Nils Stinnesbeck Date: Sun, 25 Oct 2026 22:33:44 +0100 Subject: [PATCH] SPECS: InfluxDB manifests apply as unchanged (confirmed) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01LhzAVaUyqcw5PkGjz4mWW6 --- SPECS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SPECS.md b/SPECS.md index 10c4229..552861a 100644 --- a/SPECS.md +++ b/SPECS.md @@ -141,8 +141,8 @@ tyre pressures, GPS (lat, lon, elevation, heading) and the is_* flags. It does * - 2026-10-25 — `k8s/influxdb.yaml`: the values Kubernetes fills in itself are written out — the NetworkPolicy port's `protocol: TCP`, and `apiVersion`, `kind` and `volumeMode: Filesystem` on the StatefulSet's volume claim template. Without them every `kubectl apply -k k8s/` reported - both as "configured" while `kubectl diff -k k8s/` was empty (owner). Expected: "unchanged". - Validated offline (kustomize + kubeconform); not applied by me. Also found: the in-app update + both as "configured" while `kubectl diff -k k8s/` was empty (owner). Applied by the owner: + both now "unchanged". Validated offline (kustomize + kubeconform). Also found: the in-app update check failed with an IOException because the cluster's `FORGE_TOKEN` was still the template placeholder — the forge refuses it and the server answers 502; `apply -k` does not include the Secrets, so a new token needs `kubectl apply -f k8s/secrets/secrets.yaml` and a restart.