tenant-engine/workplans/TEN-WP-0013-wave2-resource-right-sizing.md

id	type	title	domain	repo	status	flavor	owner	topic_slug	created	updated	related	state_hub_workstream_id
TEN-WP-0013	workplan	Wave-2 resource right-sizing from the 2026-10-21 allocation review	infotech	tenant-engine	finished	implementation	claude	netkingdom	2026-10-21	2026-10-21	CUST-WP-0071 RESOURCE-WP-0008	50a890de-b646-55a7-91b7-b67430c5d32a

TEN-WP-0013 — Wave-2 resource right-sizing from the 2026-10-21 allocation review

Receiving workplan in tenant-engine 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: TEN-WP-0013-T01
status: done
priority: medium
state_hub_task_id: "434773a4-2daa-51c3-a322-d314ff54ae36"

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
tenant-engine/tenant-engine	1	25m → 5m	300m	2.4/2.6	48Mi → 48Mi	192Mi	53.1/67.8	0.0	decrease

Source and container detail:

• tenant-engine/tenant-engine: Deployment tenant-engine, container tenant-engine, deploy/base/tenant-engine.yaml (25m/48Mi, limits 300m/192Mi). Memory p95 53Mi is slightly above the 48Mi request (below the change threshold); the owner may raise it to 64Mi.

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.

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).

• Live source: rapp-tenant-engine (SSA field manager rapp-tenant-engine). tenant-engine/deploy/base is not the deployed copy and was left unchanged.
• Change: rapp-tenant-engine 73deac4 (manifests/tenant-engine.yaml): CPU request 25m -> 5m. Memory stays 48Mi, limits unchanged.
• Diff: resource fields only (requests.cpu). Tests pass.
• Apply: cd ~/rapp-tenant-engine && make deploy.

Applied — 2026-10-22 (TEN-WP-0013-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. Server-side apply with field manager rapp-tenant-engine; Ready. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.