From c855e53b9ee6232f25f70b295236858d80711a74 Mon Sep 17 00:00:00 2001
From: Vladimir Kuznichenkov <kuzaxak.tech@gmail.com>
Date: Sat, 18 Sep 2021 12:36:22 +0300
Subject: [PATCH] Add empty objects to default envs to prevent validation
 errors

In case of S3 we can use IAM role to access bucket, in that case we do not need to define anything in secrets. At the same time due to missed parent level field chart will fail with an error.
---
 values.yaml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/values.yaml b/values.yaml
index 39a42b4..e239d58 100644
--- a/values.yaml
+++ b/values.yaml
@@ -61,6 +61,7 @@ persistence:
   enabled: false
   size: 10Gi
   # storageClass: '-'
+  deleteEnabled: false
 
 # set the type of filesystem to use: filesystem, s3
 storage: filesystem
@@ -70,6 +71,10 @@ storage: filesystem
 secrets:
   haSharedSecret: ""
   htpasswd: ""
+  azure: {}
+  s3: {}
+  swift: {}
+
 # Secrets for Azure
 #   azure:
 #     accountName: ""
@@ -86,6 +91,7 @@ secrets:
 #     username: ""
 #     password: ""
 
+s3: {}
 # Options for s3 storage type:
 # s3:
 #  region: us-east-1
@@ -94,6 +100,7 @@ secrets:
 #  encrypt: false
 #  secure: true
 
+swift: {}
 # Options for swift storage type:
 # swift:
 #  authurl: http://swift.example.com/