Complete M8.1 with per-worker storage probe results

Record the maintainer-run local-path probe on all three workers
(1.9-2.5 ms synchronous 4 KiB writes, 29-36 ms mean object publication,
110-255 MB/s sequential), well inside the lease deadlines, and flag
worker-3's 87% full root filesystem. Apply the maintainer's corrections:
about 500 GB more host RAM, AEvolution PostgreSQL on a separate VM
outside Kubernetes, and manual-only inventory collection. Storage
figures stay provisional until the planned RAID change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-29 12:33:04 -04:00
co-authored by Claude Opus 5.5
parent 2475563959
commit 18708340c3
5 changed files with 121 additions and 65 deletions
+19
View File
@@ -2620,3 +2620,22 @@ Evidence:
every Argo path and has **not yet been applied**, because this workstation has
no kubeconfig. The maintainer approved running it. Its results go in
INVENTORY.md.
## M8.1c storage probe and corrections - 2026-09-29
- The maintainer applied `deploy/kubernetes/inventory/disk-probe-local-path.yaml`
by hand on the cluster, and all three Jobs completed. The resources were then
deleted.
- worker-1: 1906 µs dsync, 28.7/60.6 ms object publish, 1003 ms for 256 MiB.
- worker-2: 2511 µs, 36.0/73.4 ms, 2122 ms.
- worker-3: 2239 µs, 32.1/61.0 ms, 2339 ms. Its root filesystem is 87 % full.
Every `local-path` volume is on the node's root LVM ext4 volume. The figures are
provisional until the planned RAID change.
- Corrections from the maintainer:
- Host RAM was increased by about 500 GB, so the earlier "about 20 GiB left"
estimate is withdrawn.
- AEvolution's PostgreSQL is a separate VM outside Kubernetes, reached through
`aevolution-db`.
- Collection is manual, with no automation planned.
- No credential values were read. The 18.6 version, role and TLS requirements are
enforced by the adapter and migrations when M8.3 connects.