From 7a937dae077835b7eb6976d789a53f765400b82e Mon Sep 17 00:00:00 2001 From: Jeffrey Smeets Date: Sat, 29 Aug 2026 18:00:28 +0200 Subject: [PATCH] gitea: drop the orphaned runner pvc that could never bind gitea-runner-pvc referenced volumeName gitea-runner-data, but neither that PV nor a Longhorn volume of that name exists, so it sat Pending since May. ArgoCD treats a Pending PVC as Progressing and rolled that up to the whole app, which is why gitea never reported Healthy. Nothing mounted it. The runner uses the PVC the gitea/actions chart generates from its own volumeClaimTemplate. --- .../runner/gitea-runner-persistentvolumeclaim.yaml | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 applications/gitea/runner/gitea-runner-persistentvolumeclaim.yaml diff --git a/applications/gitea/runner/gitea-runner-persistentvolumeclaim.yaml b/applications/gitea/runner/gitea-runner-persistentvolumeclaim.yaml deleted file mode 100644 index d138f18..0000000 --- a/applications/gitea/runner/gitea-runner-persistentvolumeclaim.yaml +++ /dev/null @@ -1,13 +0,0 @@ -apiVersion: v1 -kind: PersistentVolumeClaim -metadata: - name: gitea-runner-pvc - namespace: gitea -spec: - accessModes: - - ReadWriteOnce - storageClassName: longhorn-static - volumeName: gitea-runner-data - resources: - requests: - storage: 20Gi