access-engine/workplans/FLEX-WP-0038-wave2-resource-right-sizing.md
tegwick 0344b2a962
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
chore(consistency): write back State Hub ids
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-21 12:29:11 +02:00

45 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

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