Applying PR suggestion on spec.configuration change

minio · Aug 1, 2024 · 23df60b · 23df60b
1 parent 4275338
commit 23df60b
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/source/operations/install-deploy-manage/upgrade-minio-operator.rst b/source/operations/install-deploy-manage/upgrade-minio-operator.rst
@@ -42,7 +42,8 @@ The following changes apply for Operator v5.0.0 or later:
 - The ``.spec.s3`` field is replaced by the ``.spec.features`` field.
 - The ``.spec.credsSecret`` field is replaced by the ``.spec.configuration`` field.
 
-  The ``.spec.configuration`` secret should hold all the environment variables for the MinIO deployment that contain sensitive information and should not show in ``.spec.env``.
+  The ``.spec.configuration`` secret holds all of the :ref:`environment variables <minio-environment-variables>` for the MinIO deployment.
+  Using a ``.spec.configuration`` secret is preferred over ``.spec.env`` as it limits the risk of exposing sensitive variables.
   This change impacts the Tenant :abbr:`CRD (CustomResourceDefinition)` and only impacts users editing a tenant YAML directly, such as through Helm or Kustomize.
 - Both the **Log Search API** (``.spec.log``) and **Prometheus** (``.spec.prometheus``) deployments have been removed.
   However, existing deployments are left running as standalone deployments / statefulsets with no connection to the Tenant CR.