tegwick
796a1557e9
Some checks failed
Use-case regression gate / usecase-regressions (push) Failing after 2m1s
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
60 lines
3.9 KiB
Markdown
60 lines
3.9 KiB
Markdown
---
|
|
id: CSOC-WP-0017
|
|
type: workplan
|
|
title: "Wave-2 resource right-sizing from the 2026-10-21 allocation review"
|
|
domain: communication
|
|
repo: coulomb-social
|
|
status: finished
|
|
flavor: implementation
|
|
owner: claude
|
|
topic_slug: coulomb-social
|
|
created: "2026-10-21"
|
|
updated: "2026-10-21"
|
|
related:
|
|
- CUST-WP-0071
|
|
- RESOURCE-WP-0008
|
|
state_hub_workstream_id: "e8f6f027-c245-5878-9911-5fc3dcc35426"
|
|
---
|
|
|
|
# CSOC-WP-0017 — Wave-2 resource right-sizing from the 2026-10-21 allocation review
|
|
|
|
Receiving workplan in `coulomb-social` 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
|
|
|
|
```task
|
|
id: CSOC-WP-0017-T01
|
|
status: done
|
|
priority: medium
|
|
state_hub_task_id: "2d845436-34c9-58a3-97a7-46ee300da903"
|
|
```
|
|
|
|
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 |
|
|
|---|---:|---:|---:|---:|---:|---:|---:|---:|---|
|
|
| `coulomb-social/coulomb-social` | 1 | 100m → **15m** | 1000m | 0.4/24.6 | 256Mi → **176Mi** | 1024Mi | 146.2/146.3 | 0.0 | decrease + memory down |
|
|
|
|
Source and container detail:
|
|
|
|
- `coulomb-social/coulomb-social`: Deployment `coulomb-social`; `resources` in `railiance-apps/charts/coulomb-social/values.yaml` (100m/256Mi) — the chart lives in railiance-apps.
|
|
|
|
**Prepared 2026-10-21 (wave-2 worker W1a; not applied).** Live owner is Helm release `coulomb-social` (rev 16) from railiance-apps. Change: railiance-apps `b7fb7b2`, `helm/coulomb-social-values.yaml` requests 100m/256Mi → 15m/176Mi; limits stay 1000m/1Gi. The full render against live shows only `resources.requests`. Apply: `cd railiance-apps && COULOMB_SOCIAL_IMAGE_TAG=dd83c90 make coulomb-social-deploy`. The digest is pinned in the values. Strategy is Recreate, so expect a short outage while the pod restarts.
|
|
|
|
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 (CSOC-WP-0017-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. railiance-apps `make coulomb-social-deploy`, Helm revision 17. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.
|