From bf9558539a549835154c2b240ec4fd93ea617ab4 Mon Sep 17 00:00:00 2001 From: jgrusewski Date: Sun, 21 Jun 2026 17:03:04 +0200 Subject: [PATCH] fix(infra): gitea mem limit 512Mi->2Gi + Recreate strategy (Phase 2B) - 2Gi: indexing the 876MB foxhunt pack OOMKilled at 512Mi (exit 137) - Recreate: RWO PVC (sbs-default-retain) can't RollingUpdate (Multi-Attach deadlock) --- infra/k8s/gitea/values.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/infra/k8s/gitea/values.yaml b/infra/k8s/gitea/values.yaml index c5b371203..51c6e2d8d 100644 --- a/infra/k8s/gitea/values.yaml +++ b/infra/k8s/gitea/values.yaml @@ -4,6 +4,11 @@ replicaCount: 1 image: rootless: true +# RWO PVC (sbs-default-retain) → only one pod can mount it. RollingUpdate deadlocks (new pod can't +# attach while old holds it). Recreate terminates old before starting new. +strategy: + type: Recreate + # Disable all bundled subcharts — reuse the existing in-cluster postgres, no redis/memcached. postgresql: enabled: false @@ -25,8 +30,8 @@ persistence: storageClass: sbs-default-retain resources: - requests: { cpu: 100m, memory: 128Mi } - limits: { cpu: "1", memory: 512Mi } + requests: { cpu: 100m, memory: 256Mi } + limits: { cpu: "1", memory: 2Gi } # 2Gi headroom: indexing the 876MB foxhunt pack OOMed at 512Mi service: http: { type: ClusterIP, port: 3000 }