fix: adding an environment value to enable the ignoring of the name, …

…accessKey and secretKey in configSecret.

In version 6.0.4 the inclusion of [this check](https://github.com/minio/operator/pull/2299/files#diff-1320c71ce4251e5e50c3b17c8aee11659e44a7208d1ab8d5c4f68694c02d9e80R20-R25) broke the ability to pass an existing secret because the default values provided in the values.yaml file, caused the error to trigger. Now we can presume in dev that the vluaes will be provided in line and in prod, they are provided via an existing secret.

helm/tenant/templates/tenant-configuration.yaml

@@ -17,6 +17,7 @@ stringData:
     export MINIO_ROOT_PASSWORD={{ .Values.tenant.configSecret.secretKey | quote }}
 
 {{- else }}
+{{- if eq .Values.tenant.environment "dev" }}
 {{- if (.Values.tenant.configSecret.accessKey) }}
 {{- fail "# ERROR: cannot set access-key when an existing secret is used" }}
 {{- end }}
@@ -26,4 +27,5 @@ stringData:
 {{- end }}
 {{- end }}
 {{- end }}
+{{- end }}
 

helm/tenant/values.yaml

@@ -47,6 +47,15 @@ tenant:
   # The secret is expected to have a key named config.env containing environment variables exports.
   configuration:
     name: myminio-env-configuration
+
+  ###
+  # The environment into which this tenant will be deployed.
+  # Valid options:
+  #
+  # environment: dev # will presume you are using the config secret in line as shown below.
+  # environment: prod # will ignore the name, accessKey and secretKey fields and enforce the existing option.
+  environment: dev
+
   ###
   # Root key for dynamically creating a secret for use with configuring root MinIO User
   # Specify the ``name`` and then a list of environment variables.