issue-core/workplans/ISSUE-WP-0008-wave2-resource-right-sizing.md

id	type	title	domain	repo	status	flavor	owner	topic_slug	created	updated	related	state_hub_workstream_id
ISSUE-WP-0008	workplan	Wave-2 resource right-sizing from the 2026-10-21 allocation review	infotech	issue-core	finished	implementation	claude	issue-core	2026-10-21	2026-10-21	CUST-WP-0071 RESOURCE-WP-0008	2e38eb47-173d-5590-bf2d-1e8a22d0b2e7

ISSUE-WP-0008 — Wave-2 resource right-sizing from the 2026-10-21 allocation review

Receiving workplan in issue-core for the wave-2 request changes below.

Origin: the 2026-10-21 node allocation review (RESOURCE-WP-0008-T03, feeding CUST-WP-0071-T03). Per the founder's 2026-10-21 delivery interview (the-custodian/docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md) the small adjustments form wave 2: one receiving task per owner repo, applied later in a batch. Applying wave 2 needs a separate founder approval, so every cluster-write task here is a human-gated wait. This file changes no manifest.

Apply the reviewed request changes

id: ISSUE-WP-0008-T01
status: done
priority: medium
state_hub_task_id: "a208bfad-9c95-53f3-9f0f-8bfadddf844c"

Values are pod-aggregate figures from the budget file (7-day window ending 2026-10-21T06:08Z). Limits stay unchanged unless stated.

Workload (ns/name)	Pods	CPU request	CPU limit	CPU p95/peak 7d (m)	Memory request	Memory limit	Mem p95/peak (Mi)	Throttle	Action
issue-core/issue-core	1	50m → 5m	500m	2.0/3.4	128Mi → 48Mi	256Mi	41.4/50.7	0.0	decrease + memory down

Source and container detail:

• issue-core/issue-core: Deployment issue-core, container issue-core, rapp-issue-core/manifests/30-runtime.yaml (50m/128Mi) — the deploy source lives in rapp-issue-core.

Prepared 2026-10-21 (wave-2 worker W1a; not applied). Live owner is ArgoCD Application issue-core (manual sync, rapp-issue-core manifests). Change: rapp-issue-core 11af3cb, manifests/30-runtime.yaml requests 50m/128Mi → 5m/48Mi, limits unchanged. Pin: railiance-platform 30c48cb moves argocd/railiance01/applications/issue-core.application.yaml targetRevision 805e124 → 11af3cb. Neither change is pushed or synced. The full manifest set against live shows only resources.requests on the Deployment. Apply: push rapp-issue-core, push railiance-platform (the root app updates the Application), then run a manual sync of issue-core. RollingUpdate.

Evidence: resource-control docs/evidence/2026-10-21-node-allocation-review/2026-10-21-node-budget.md (+ .json, commit 3d9b1bd). Rule: CPU = max(floor, p95x1.5, peakx0.5) rounded up to 5m; memory request = 7d p95 working set x1.15 (only when the change is at least 64Mi).

Steps:

1. Map the pod-aggregate proposal onto the named container(s) in the source file; where a workload has several containers or pods, split by the per-pod figures in 2026-10-21-workload-usage.json and keep the sum at the proposed value.
2. Prepare the source change as a reviewed commit (no push, no sync) and record the before values here.
3. Apply only inside the batched wave-2 rollout, after founder approval, through the owner's normal deploy path (ArgoCD sync or documented helm/kubectl apply).

Verification: kubectl -n <ns> 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.

Applied — 2026-10-22 (ISSUE-WP-0008-T01)

Applied under the founder's wave-2 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), after a full-render diff against live that showed resources only. ArgoCD pin rapp-issue-core 11af3cb (railiance-platform 30c48cb), manual sync; Synced and Healthy. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.