RAPPS-WP-0019 finished; forge runner memory limit
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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:46:40 +02:00
parent db0ade1cf3
commit 1dd7387cbc
4 changed files with 23 additions and 9 deletions

View file

@ -23,7 +23,7 @@ Hostname decision: `the-custodian/docs/forgejo-production-decisions.md`.
| Server | railiance01 `92.205.62.239` |
| Namespace | `forgejo` |
| Helm release | `forgejo` |
| HTTP service | `forgejo-gitea-http` (chart naming; ingress must target this) |
| HTTP service | `forge-http` (chart naming; ingress must target this) |
| Chart | `gitea-charts/gitea` **12.5.0** (Forgejo-compatible; 12.6+ needs Gitea 1.26 `config edit-ini`) |
| Image | `code.forgejo.org/forgejo/forgejo:11.0.3` |
| Database | `forgejo-db-rw.databases.svc.cluster.local:5432` |
@ -71,7 +71,7 @@ make forgejo-runner-status
- `strategy.type: Recreate` in `helm/forgejo-values.yaml` — avoids leveldb queue lock
on the shared RWO PVC during rolling updates.
- Actions enabled via `gitea.config.actions.ENABLED: true`.
- Ingress backend service name is `forgejo-gitea-http` (Helm release naming).
- Ingress backend service name is `forge-http` (Helm release naming).
## Day-2 operator targets