stack.basicstack.de/apps/forgejo
CTO Agent ef5ef56784 Fix Forgejo deployment hanging in Argo CD sync
Change deployment strategy from RollingUpdate (default) to Recreate
to resolve volume attachment conflict. The forgejo-data PVC uses
ReadWriteOnce access mode, which only allows attachment to one pod
at a time. RollingUpdate tries to start new pod before terminating
old pod, causing multi-attach error.

With Recreate strategy, old pod terminates first, volume detaches,
then new pod starts and successfully attaches the volume.

Resolves: DEV-380

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-07-25 15:25:23 +00:00
..
forgejo-deployment.yaml Fix Forgejo deployment hanging in Argo CD sync 2026-07-25 15:25:23 +00:00
forgejo-ingress.yaml Add Forgejo deployment manifests for Argo CD GitOps 2026-07-12 13:55:47 +00:00
forgejo-postgres-secret-sealed.yaml apps/forgejo/forgejo-postgres-secret-sealed.yaml aktualisiert 2026-07-12 14:10:45 +00:00
forgejo-postgres-service.yaml Add Forgejo deployment manifests for Argo CD GitOps 2026-07-12 13:55:47 +00:00
forgejo-postgres-statefulset.yaml Add Forgejo deployment manifests for Argo CD GitOps 2026-07-12 13:55:47 +00:00
forgejo-pvc.yaml Add Forgejo deployment manifests for Argo CD GitOps 2026-07-12 13:55:47 +00:00
forgejo-service.yaml Add Forgejo deployment manifests for Argo CD GitOps 2026-07-12 13:55:47 +00:00