gitea fix

2026-08-31 01:31:44 +05:30
parent 0410e91ce7
commit 786d88a61e
1 changed files with 13 additions and 0 deletions
@@ -12,6 +12,19 @@ gitea:
  # persistence.size must stay 10Gi to match the already-bound PVC —
  # local-path-provisioner doesn't support volume expansion.
  # Chart default is RollingUpdate with maxUnavailable: 0 — the new pod
  # always comes up before the old one terminates. On a real multi-node
  # cluster with real RWO block storage that's fine (the new pod just
  # can't mount until the old one releases). On this single-node cluster,
  # local-path-provisioner's hostPath-style volume doesn't block a second
  # same-node mount, so old+new pods briefly run concurrently against the
  # same /data — and Gitea's LevelDB-backed queue holds an exclusive file
  # lock, so the new pod crashes with "unable to lock level db ...
  # resource temporarily unavailable". Recreate forces the old pod to
  # fully terminate (and release the lock) before the new one starts.
  strategy:
    type: Recreate
  persistence:
    size: 10Gi