Record RAIL-EN-WP-0002-T02 applied: ArgoCD pods Burstable on railiance01.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 19:10:13 +02:00
parent e01083da79
commit 1a3db13788

View file

@ -46,7 +46,7 @@ declared base matches live exactly.
```task
id: RAIL-EN-WP-0002-T02
status: wait
status: done
priority: high
state_hub_task_id: "8846994d-24cf-58e4-83ea-c8b23610bf22"
```
@ -65,8 +65,9 @@ Added requests: 95m CPU, 480Mi memory. Node requests before: 3320m (83%) CPU,
8856Mi (55%) memory, so this fits. Pods become Burstable. Idle use is with 0
Applications; revisit after phase B adoption.
This is a **live change** (rolls all four pods). It is not taken in this
session. On the founder's go-ahead, mode `ADMINISTER @ realm:kubernetes/railiance01`,
**Applied 2026-09-21** (founder go-ahead; custodian session, `ADMINISTER @ realm:kubernetes/railiance01`, `activation=APPROVED`): `argocd-diff` showed resources-only; 680m CPU free and 0 Pending beforehand; 34 objects server-side applied; all four rollouts complete; all four pods Burstable, Ready, 0 restarts; 0 Pending after.
This was a **live change** (rolls all four pods). On the founder's go-ahead, mode `ADMINISTER @ realm:kubernetes/railiance01`,
`activation=APPROVED`:
```bash