nils/mg4
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

SPECS: InfluxDB manifests apply as unchanged (confirmed)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LhzAVaUyqcw5PkGjz4mWW6
This commit is contained in:
nils
2026-10-25 22:33:44 +01:00
co-authored by Claude Opus 5.5
parent d865906859
commit 76a6213126
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SPECS.md
+2 -2
View File
@@ -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 - 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 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 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". both as "configured" while `kubectl diff -k k8s/` was empty (owner). Applied by the owner:
Validated offline (kustomize + kubeconform); not applied by me. Also found: the in-app update 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 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 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. the Secrets, so a new token needs `kubectl apply -f k8s/secrets/secrets.yaml` and a restart.