From 36b794a94e95b5f90ad680e78daec96c60f70ddf Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sun, 12 Jul 2026 17:13:26 +0000 Subject: [PATCH] Document mysql-data-encrypted PVC as pre-existing, unmanaged resource The mysql-data-encrypted PVC exists in the cluster and is working correctly, but attempting to manage it through Argo CD causes sync failures because the PVC is already bound and its spec is immutable. Leaving it unmanaged while documenting its existence. Co-Authored-By: Paperclip --- apps/bookstack/bookstack-deployment.yaml | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/apps/bookstack/bookstack-deployment.yaml b/apps/bookstack/bookstack-deployment.yaml index 97baace..2159704 100644 --- a/apps/bookstack/bookstack-deployment.yaml +++ b/apps/bookstack/bookstack-deployment.yaml @@ -62,20 +62,7 @@ spec: persistentVolumeClaim: claimName: mysql-data-encrypted --- -# MySQL Data PersistentVolumeClaim -apiVersion: v1 -kind: PersistentVolumeClaim -metadata: - name: mysql-data-encrypted - namespace: bookstack -spec: - accessModes: - - ReadWriteOnce - storageClassName: hcloud-volumes-encrypted - resources: - requests: - storage: 20Gi ---- +# Note: mysql-data-encrypted PVC is pre-existing and not managed by Argo CD # MySQL Service apiVersion: v1 kind: Service