ops: complete host-operator ramp-up on railiance01 (WP-0009 T10)
Live observe session verified SSH access, captured baseline and Critical health/load findings (memory pressure, k3s API unavailable). RU checklist closed; engagement phase operating; schedule enabled; no privileged changes.
This commit is contained in:
parent
7257e62dba
commit
6ca167ce19
15 changed files with 334 additions and 90 deletions
|
|
@ -1,7 +1,13 @@
|
|||
# Outstanding risks — eng-coulomb-railiance01-ho-001
|
||||
|
||||
_Populated during operate and finalised at ramp-down (RD-03)._
|
||||
Populated during operate; finalise at ramp-down (RD-03).
|
||||
|
||||
| Risk | Severity | Mitigation / owner | Status |
|
||||
|------|----------|--------------------|--------|
|
||||
| _none recorded_ | | | |
|
||||
| RAM undersized (3.8G, no swap) for k3s+platform density | Critical | Human capacity decision (RAM and/or swap); reduce concurrent load | open |
|
||||
| k3s API ServiceUnavailable under pressure | Critical | Stabilize memory; re-check API; avoid heavy kubectl while degraded | open |
|
||||
| Load average ≫ 2 cores | High | Same as capacity; schedule non-urgent work off-host | open |
|
||||
| journald ~4.1G | Medium | Approved journal vacuum | open |
|
||||
| Pending security package updates | Medium | Approved OS security pass | open |
|
||||
| UFW allows 6443/8472 from Anywhere | Medium | Policy review + possible firewall_change | open |
|
||||
| Reverse-forward port 18765 collisions | Low–Medium | Bridge/tunnel cleanup | open |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue