Enable Forgejo Actions and Recreate deployment strategy

Actions are required for CI runners. Recreate avoids leveldb queue lock
contention on the shared PVC during Helm upgrades.
This commit is contained in:
tegwick 2026-07-03 21:44:57 +02:00
parent 75698636c6
commit f49be83f7e
2 changed files with 15 additions and 1 deletions

View file

@ -60,6 +60,14 @@ make forgejo-status
make forgejo-smoke make forgejo-smoke
``` ```
## Upgrade notes
- Pin `FORGEJO_CHART_VERSION=12.5.0` — chart 12.6+ requires Gitea 1.26 `config edit-ini`.
- `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).
## Day-2 operator targets ## Day-2 operator targets
```bash ```bash

View file

@ -1,5 +1,9 @@
# Non-secret Forgejo Helm values (gitea-charts/gitea chart + Forgejo image). # Non-secret Forgejo Helm values (gitea-charts/gitea chart + Forgejo image).
# Layer helm/forgejo-secrets.sops.yaml for database password and admin credentials. # Layer helm/forgejo-secrets.sops.yaml for database password and admin credentials.
# Recreate avoids leveldb queue lock fights on the shared RWO PVC during upgrades.
strategy:
type: Recreate
service: service:
http: http:
type: ClusterIP type: ClusterIP
@ -44,4 +48,6 @@ gitea:
SSH_LISTEN_PORT: 2222 SSH_LISTEN_PORT: 2222
DISABLE_SSH: false DISABLE_SSH: false
service: service:
DISABLE_REGISTRATION: true DISABLE_REGISTRATION: true
actions:
ENABLED: true