---
id: FLEX-WP-0038
type: workplan
title: "Wave-2 resource right-sizing for the flex-auth runtime"
domain: infotech
repo: access-engine
status: ready
flavor: implementation
owner: access-engine
created: "2026-10-21"
updated: "2026-10-21"
related: [CUST-WP-0071, RESOURCE-WP-0008]
state_hub_workstream_id: "90ae025e-8102-5dfe-9461-7590f2b3fd3e"
---

# Wave-2 resource right-sizing for flex-auth

Receiving record for the node-level allocation review of RESOURCE-WP-0008
(resource-control `3d9b1bd`). Evidence:
`resource-control/docs/evidence/2026-10-21-node-allocation-review/2026-10-21-node-budget.{md,json}`.
The founder placed this task in access-engine, beside `charts/flex-auth`, on
2026-10-21 (`the-custodian/docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md`).

```task
id: FLEX-WP-0038-T01
status: wait
priority: low
needs_human: true
blocking_reason: "Wave-2 cluster write needs founder approval (2026-10-21 interview)."
state_hub_task_id: "0ed6cd93-972e-56de-b6c8-0528249c90ae"
```

| Workload | Pods | CPU request (m) | CPU limit (m) | 7d CPU p95/peak (m) | Memory request (Mi) | 7d memory p95/peak (Mi) |
|---|---:|---|---:|---|---|---|
| flex-auth/flex-auth | 9 | 145 → 45 | 2700 | 2.2 / 18.6 | 288 → 176 | 140 / 191 |

Proposed values follow the review rule: the largest of p95×1.5, peak×0.5 and the
per-pod floor. Spread them across the 9 pods in the chart's existing resource
values (`charts/flex-auth/values.yaml`). Find the deployed values override first,
and check that the chart actually produces the live objects.

Verify: every flex-auth pod is Ready, with no restarts or OOM kills over 24 hours,
authorization decision latency is unchanged, and the next weekly allocation report
shows no CPU throttling. Rollback: revert the values commit and redeploy through
the existing path.