From 62496cb4e03daca7d63d80cf1388eb9d68f6c0b6 Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 22 Oct 2026 00:09:06 +0200 Subject: [PATCH] Wave-2 right-sizing: record prepared change, diff verdict and apply command Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 276069@bnt-lap001 Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c --- .../ACTIVITY-WP-0049-wave2-resource-right-sizing.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/workplans/ACTIVITY-WP-0049-wave2-resource-right-sizing.md b/workplans/ACTIVITY-WP-0049-wave2-resource-right-sizing.md index 315fdc0..3abc6fe 100644 --- a/workplans/ACTIVITY-WP-0049-wave2-resource-right-sizing.md +++ b/workplans/ACTIVITY-WP-0049-wave2-resource-right-sizing.md @@ -54,3 +54,14 @@ Steps: Verification: `kubectl -n get pod -o jsonpath='{..resources}'` shows the new requests; pods Ready with no new restarts or OOMKilled over 24h; for CPU decreases the throttle ratio and request latency stay at or below the 7d baseline; node request total drops by the expected delta. Rollback: revert the source commit and re-sync/re-apply; the before values in the table above are the rollback target. Keep before/after `kubectl get -o yaml` captures as the receipt. + +## Prepared 2026-10-22 (wave-2 worker W1b) + +Status stays `wait` / `needs_human`. Local commit only: not pushed, not applied. Diff = full owner render vs live (`kubectl diff`, object names and changed key paths only, Secret objects skipped). + +- Totals kept at the proposal, 100m CPU / 944Mi memory over the 10 live pods (requests only, no new limits): api 5m/96Mi, worker 5m/176Mi, event-router 5m/80Mi, statehub-edge-relay 50m/128Mi -> 10m/96Mi, temporal 35m/240Mi, temporal-ui 5m/16Mi, nats 5m/16Mi, app-db 10m/48Mi, temporal-db 15m/128Mi, llm-connect 50m/128Mi -> 5m/48Mi. +- Commits: activity-core `d3cd1a2` (`k8s/gitops/runtime.yaml`, `k8s/railiance/10-infrastructure.yaml`, `k8s/railiance/20-runtime.yaml`) and llm-connect `19006db` (`deploy/k8s/activity-core-llm-connect/deployment.yaml`). +- Diff: resource fields only for all objects. The local diff of the gitops render also drops the ArgoCD tracking-id annotation, which is expected. Existing drift: the source already declared app-db/temporal-db 50m/256Mi requests and a 1Gi memory limit that were never applied. Applying 10-infrastructure therefore also adds that owner-declared 1Gi memory limit to both DBs, which the founder should confirm. +- Restart: yes. app-db and temporal-db (single-replica postgres StatefulSets), nats, temporal, temporal-ui, relay, api, worker, event-router and llm-connect all roll. +- Gates: (1) api/worker/event-router are ArgoCD-managed with `targetRevision` pinned in `railiance-platform/argocd/railiance01/applications/activity-core.application.yaml`, so after push the pin needs a bump. That repo is owned by another worker. (2) `scripts/check_gitops_promotion.py` is an image-only admission policy and refuses a resources-only gitops change. The founder needs to accept the exception. +- Apply: `kubectl apply -f k8s/railiance/10-infrastructure.yaml`; apply only the relay Deployment from `20-runtime.yaml`, not the whole file, because it holds immutable Jobs and ArgoCD-owned Deployments; `kubectl apply -k ~/llm-connect/deploy/k8s/activity-core-llm-connect`; then bump the ArgoCD pin and sync `activity-core`.