Final fixup

helm/tenant/values.yaml

@@ -1,6 +1,12 @@
 ###
-# Root key for setting secrets for use with configuring root MinIO User
-# For development or PoC deployments, you can dynamically create the secret by specifying the ``name`` and then a list of environment variables. 
+# Root key for dynamically creating a secret for use with configuring root MinIO User
+# Specify the ``name`` and then a list of environment variables. 
+#
+# .. important::
+#
+#    Do not use this in production environments. 
+#    This field is intended for use with rapid development or testing only.
+# 
 # For example:
 #
 # .. code-block:: yaml
@@ -9,8 +15,15 @@
 #    accessKey: minio
 #    secretKey: minio123
 #
-# For production you can specify the name of an existing opaque secret to ``existingSecret``.
-# The secret must contain a key ``config.env`` that resembles the following
+secrets:
+  name: myminio-env-configuration
+  accessKey: minio 
+  secretKey: minio123
+###
+# The name of an existing Kubernetes secret to import to the MinIO Tenant
+# The secret must contain a key ``config.env``.
+# The values should be a series of export statements to set environment variables for the Tenant.
+# For example:
 #
 # .. code-block:: shell
 #
@@ -19,10 +32,6 @@
 #         export MINIO_ROOT_USER=ROOTUSERNAME
 #         export MINIO_ROOT_PASSWORD=ROOTUSERPASSWORD
 #
-secrets:
-  name: myminio-env-configuration
-  accessKey: minio 
-  secretKey: minio123
 existingSecret:
   name: myminio-env-configuration
 ###