Record M8.1 cluster inventory and per-worker storage probe

Summarize the maintainer-collected read-only inventory: RKE2 v1.32.5,
an untainted control plane and three 32 GB workers on one hypervisor,
no kubelet reservations or quotas, local-path as the only (node-pinned,
reclaim Delete) storage, Canal/ingress-nginx/MetalLB/cert-manager, a
manually synced aevolution-dev application and no PostgreSQL 18.6.
Propose a measured budget and dev placement, and add a ready-to-apply
local-path probe with one PVC and Job pinned to each worker.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-29 12:20:45 -04:00
co-authored by Claude Opus 5.5
parent 680e7e5725
commit 2475563959
5 changed files with 470 additions and 45 deletions
+20
View File
@@ -2600,3 +2600,23 @@ Evidence:
three owners in Release: peak RSS 9,940 KiB, and 60 ms CPU over 16.3 s of
serving. The full PostgreSQL Release suite passed with it. The analysis build
compiled clean, and the format check passed.
## M8.1b cluster inventory - 2026-09-29
- The maintainer ran `tools/inventory/collect-cluster.sh`. It made read requests
only, and listed Secrets as name, type and key count. The output is in
`C:\tmp\cluster` on the workstation and is not committed. The results are
summarized in docs/infrastructure/INVENTORY.md:
- RKE2 v1.32.5 with one untainted control plane (6 vCPU / 11.7 GiB) and three
workers (8 vCPU / 31.3 GiB).
- No kubelet reservations, quotas or LimitRanges.
- Storage is `local-path` only (reclaim Delete, no CSI, no snapshots).
- Canal/Calico, ingress-nginx, MetalLB and cert-manager with Let's Encrypt.
- `aevolution-dev` has no automated sync.
- No PostgreSQL 18.6 in the cluster (Gitea runs 17.6).
- The collector ran as cluster-admin. A read-only identity is an M8.2 item.
- `deploy/kubernetes/inventory/disk-probe-local-path.yaml` parses as one
NetworkPolicy and three PVC/Job pairs, pinned to worker-1..3. It is outside
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.