Add usage of zammadConfig.storageVolume.existingClaim to the 'full' t…

…est scenario for chart-testing.
zammad · Apr 18, 2024 · 3f551dd · 3f551dd
1 parent d1e7c28
commit 3f551dd
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 2 deletions.
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
@@ -125,7 +125,7 @@ jobs:
         run: kubectl create namespace zammad
 
       - name: Install secrets
-        run: kubectl create --namespace zammad --filename zammad/ci/full-secrets.yaml
+        run: kubectl create --namespace zammad --filename zammad/ci/full-objects.yaml
 
       - name: Run chart-testing (install)
         run: ct install --config .github/ct.yaml --helm-extra-args '--timeout 900s'
diff --git a/zammad/ci/full-secrets.yaml → zammad/ci/full-objects.yaml b/zammad/ci/full-secrets.yaml → zammad/ci/full-objects.yaml
@@ -37,4 +37,15 @@ data:
 kind: Secret
 metadata:
   name: autowizard
-type: Opaque
+type: Opaque
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: storage-volume-claim
+spec:
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 32Mi
diff --git a/zammad/ci/full-values.yaml b/zammad/ci/full-values.yaml
@@ -33,5 +33,8 @@ redis:
     existingSecretPasswordKey: redis-password
 
 zammadConfig:
+  storageVolume:
+    enabled: true
+    existingClaim: 'storage-volume-claim'
   minio:
     enabled: true