From 444cb127bd9f7fcd15b6eb315bb707c79cdb8538 Mon Sep 17 00:00:00 2001 From: Scooby Husky Date: Tue, 18 Aug 2026 18:24:30 -0500 Subject: [PATCH] Add missing n8n-main-persistence PVC on VPS n8n's chart uses persistence.type: existing, which expects this PVC to already exist - nothing ever created it since n8n started at replicas: 0 and is only now being scaled up to 1 (confirmed live: pod stuck Pending, 'persistentvolumeclaim n8n-main-persistence not found'). --- .../vps-standby/n8n/manifests/pvc.yaml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 infrastructure/vps-standby/n8n/manifests/pvc.yaml diff --git a/infrastructure/vps-standby/n8n/manifests/pvc.yaml b/infrastructure/vps-standby/n8n/manifests/pvc.yaml new file mode 100644 index 0000000..ae754e4 --- /dev/null +++ b/infrastructure/vps-standby/n8n/manifests/pvc.yaml @@ -0,0 +1,17 @@ +--- +# n8n's chart uses persistence.type: existing (values.yaml) - it expects +# this PVC to already exist rather than creating one itself. At home this +# PVC predates the chart deploy; on the VPS nothing ever created it since +# n8n started at replicas: 0 - found live when scaling up to 1. +apiVersion: v1 +kind: PersistentVolumeClaim +metadata: + name: n8n-main-persistence + namespace: n8n +spec: + accessModes: + - ReadWriteOnce + storageClassName: local-path + resources: + requests: + storage: 10Gi