From f85006a283ac6d5573f0f9e822b81d386c8ca071 Mon Sep 17 00:00:00 2001
From: Waqar Ahmed <waqarahmedjoyia@live.com>
Date: Sun, 6 Dec 2020 23:52:28 +0500
Subject: [PATCH] Clean values

---
 test/nextcloud/2.3.2/values.yaml | 26 --------------------------
 1 file changed, 26 deletions(-)

diff --git a/test/nextcloud/2.3.2/values.yaml b/test/nextcloud/2.3.2/values.yaml
index 3cfaf93ae11..23b90c4b829 100644
--- a/test/nextcloud/2.3.2/values.yaml
+++ b/test/nextcloud/2.3.2/values.yaml
@@ -10,7 +10,6 @@ nextcloud:
   host: nextcloud.kube.home
   username: admin
   password: changeme
-  update: 0
   datadir: /var/www/html/data
   persistence:
     subPath:
@@ -63,31 +62,6 @@ nextcloud:
   ## IMPORTANT: use with care, it is suggested to leave as that for upgrade purposes
   ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
   strategy: "Recreate"
-    # type: RollingUpdate
-    # rollingUpdate:
-    #   maxSurge: 1
-    #   maxUnavailable: 0
-
-  ##
-  ## Extra environment variables
-  extraEnv:
-  #  - name: SOME_SECRET_ENV
-  #    valueFrom:
-  #      secretKeyRef:
-  #        name: nextcloud
-  #        key: secret_key
-
-  # Extra mounts for the pods. Example shown is for connecting a legacy NFS volume
-  # to NextCloud pods in Kubernetes. This can then be configured in External Storage
-  extraVolumes:
-  #  - name: nfs
-  #    nfs:
-  #      server: "10.0.0.1"
-  #      path: "/nextcloud_data"
-  #      readOnly: false
-  extraVolumeMounts:
-  #  - name: nfs
-  #    mountPath: "/legacy_data"
 
 postgresql:
   backupVolume: