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

FORGE-WP-0011: naming follow-up resolved by RAPPS-WP-0019
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-21 23:32:08 +02:00
parent 1c916196a9
commit 9a313b7048
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
workplans/FORGE-WP-0011-forgejo-resource-requests.md
View file

@ -249,3 +249,7 @@ The founder ran the final step of `make forgejo-deploy` in their own terminal: `
- Node requests: 3840m (96%) CPU, 78% memory.
Rollback reference, if ever needed: `kubectl rollout undo deployment/forgejo-gitea -n forgejo --to-revision=14` (never `helm rollback forgejo 9`). The founder's own NetKingdom sign-in check is optional confirmation. Re-measurement after 24h/7d follows in the weekly allocation report.
## Naming follow-up resolved by RAPPS-WP-0019 — 2026-10-21
The forge objects are now named `forge`, `forge-http` and `forge-ssh`, with pod label `forge` (railiance-apps RAPPS-WP-0019, Helm revision 11). Still left in T04: a runner container memory limit and the stale Error runner pod from 66 days ago. The data volume and the container names keep their chart-imposed legacy names.