coulomb/railiance-apps
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

RAPPS-WP-0018-T01: record wave-2 preparation (not applied)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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
This commit is contained in:
tegwick 2026-10-22 00:06:57 +02:00
parent b7fb7b226f
commit 9ecb123451
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
workplans/RAPPS-WP-0018-wave2-resource-right-sizing.md
View file

@ -43,6 +43,10 @@ Source and container detail:
- `vergabe-demo-company/vergabe-teilnahme`: Deployment `vergabe-teilnahme` (container `vergabe-teilnahme`), `resources` in `helm/vergabe-demo-company-values.proposed.yaml` (60m/256Mi, limits 1000m/1Gi); the chart default in `charts/vergabe-teilnahme/values.yaml` (100m/256Mi) is not what is deployed. Keep the 60m CPU request and the 1000m/1Gi limits (replay-backed). Raise memory 256Mi → 512Mi: the target replay (`docs/evidence/2026-10-21-vergabe-target-replay/`, commit `1af6d82`, RAPPS-WP-0014-T04) showed a loaded working set of 320–480MiB.
**Prepared 2026-10-21 (wave-2 worker W1a; not applied).** Change: railiance-apps `b7fb7b2`.
- Vergabe: live Helm release `vergabe-teilnahme` in `vergabe-demo-company` (rev 3) matches `helm/vergabe-demo-company-values.proposed.yaml`. Memory request 256Mi → 512Mi for the app and the `migrate` init container, which share `resources`. CPU stays 60m and limits stay 1000m/1Gi. The full render against live adds **drift beyond resources**: the label `railiance.io/release-unit: vergabe` (from commit 64530e1, 2026-10-21) is missing on Service `vergabe-teilnahme` and both PVCs; the Deployment already has it. Because of this the apply comes to the founder. Apply: `helm upgrade vergabe-teilnahme charts/vergabe-teilnahme -n vergabe-demo-company -f helm/vergabe-demo-company-values.proposed.yaml --wait --timeout 5m`. Strategy is Recreate (short outage).
- Inter-Hub: the owner chose removal. Deleted `charts/inter-hub`, `helm/inter-hub-values.yaml`, the `inter-hub-*` Make targets, `tools/inter-hub-smoke.sh` and `.gitea/workflows/inter-hub-production-deploy.yaml`; the inter-hub part of `tools/k8s-server-dry-run.sh` is removed and the docs updated. Live: Deployment (0 replicas, 250m/512Mi), Service and 8 old ReplicaSets, all from Helm release `inter-hub` (rev 2); it has no Ingress. Apply: `helm uninstall inter-hub -n inter-hub`. Afterwards the founder checks for leftover credential objects, which agents do not inspect, before deleting the namespace. A stale rollback artifact `core-hub/k8s/railiance-production/rollback-inter-hub-ingress.yaml` (archived CORE-WP-0005) still points at the release.
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: