coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wave-2 right-sizing applied 2026-10-22 (CUST-WP-0071)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
This commit is contained in:
tegwick 2026-10-22 01:03:36 +02:00
parent 62496cb4e0
commit b7cfe087b2
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/ACTIVITY-WP-0049-wave2-resource-right-sizing.md
View file

@ -27,9 +27,9 @@ Origin: the 2026-10-21 node allocation review (`RESOURCE-WP-0008-T03`, feeding `
```task
id: ACTIVITY-WP-0049-T01
status: wait
blocking_reason: "ArgoCD part (api/worker/event-router) needs an exception to the image-only promotion check; infra, relay and llm-connect applied."
priority: medium
needs_human: true
blocking_reason: "Wave-2 cluster write; founder approval for wave 2 not yet given (2026-10-21 interview)"
state_hub_task_id: "588ffa46-5368-5479-a2f2-df8419245a77"
```
@ -65,3 +65,7 @@ Status stays `wait` / `needs_human`. Local commit only: not pushed, not applied.
- 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`.
## Applied — 2026-10-22 (ACTIVITY-WP-0049-T01)
Partial: the infrastructure is applied (app-db and temporal-db restarted, including the already-declared 1Gi memory limits), and so are the relay and llm-connect. All are Ready. The ArgoCD part (api, worker, event-router) waits: `scripts/check_gitops_promotion.py` admits image changes only, so it needs an owner exception or a promotion-check change, then a pin bump in railiance-platform. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.