ops: apply approved host-operator remediations on railiance01
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 4s
ci / test (push) Failing after 5s

Record operator approval and implement P1–P4: 4G swapfile, journald vacuum,
apt upgrade, and UFW lockdown of k3s API/flannel world-open rules. k3s node
Ready post-change; residual risk is still tight RAM.
This commit is contained in:
tegwick 2026-07-16 13:05:25 +02:00
parent 6730ec0a2c
commit 48443a9abb
8 changed files with 129 additions and 41 deletions

View file

@ -8,6 +8,6 @@
## Summary
T10 ramp-up complete: Critical memory/load, k3s API unavailable, RU all done, phase operating
Approved P1-P4 done: 4G swap, journal vacuum, apt upgrade, UFW k3s API allowlist; k3s Ready; RAM still tight
_Billing metadata only in commercial/ledger.jsonl; no secrets in this report._