Merge pull request #898 from replicatedhq/laverya/sc-58587/run-minio-…

…add-on-in-distributed-mode-so-that

document ekco's management of MinIO

src/markdown-pages/add-ons/ekco.md

@@ -29,6 +29,7 @@ spec:
     enableInternalLoadBalancer: true
     shouldDisableRestartFailedEnvoyPods: false
     envoyPodsNotReadyDuration: 5m
+    minioShouldDisableManagement: false
 ```
 
 flags-table
@@ -110,6 +111,18 @@ This has been added to work around a [known issue](https://github.com/projectcon
 This functionality can be disabled by setting the `ekco.shouldDisableRestartFailedEnvoyPods` property to `true`.
 The duration can be adjusted by changing the `ekco.envoyPodsNotReadyDuration` property.
 
+### Manage MinIO with EKCO
+
+When you install kURL with `ekco.minioShouldDisableManagement` set to `false`, the EKCO operator manages data in the MinIO deployment to ensure that the data is properly replicated and has high availability.
+
+To manage data in MinIO, the EKCO operator first enables a high availability six-replica StatefulSet when at least three nodes are healthy and the OpenEBS localpv storage class is available.
+
+Then, EKCO migrates data from the original MinIO deployment to the StatefulSet before deleting the data. MinIO is temporarily unavailable while the data migration is in progress.
+
+After the StatefulSet is running, EKCO ensures that replicas are evenly distributed across nodes.
+
+To disable EKCO's management of data in MinIO, set `ekco.minioShouldDisableManagement` to `true`.
+
 ### TLS Certificate Rotation
 
 EKCO supports automatic certificate rotation for the [registry add-on](/docs/install-with-kurl/setup-tls-certs#registry) and the [Kubernetes control plane](/docs/install-with-kurl/setup-tls-certs#kubernetes-control-plane) since version 0.5.0 and for the KOTS add-on since version 0.7.0. For more information about automatic certificate rotation for the KOTS add-on, which is used by the Replicated app manager, see [Using TLS Certificates](https://docs.replicated.com/vendor/packaging-using-tls-certs) in the Replicated documentation.

src/markdown-pages/add-ons/minio.md

@@ -27,3 +27,10 @@ flags-table
 If Rook was previously installed but is no longer specified in the kURL spec and MinIO is specified instead, MinIO will migrate data from Rook's object store to MinIO.
 
 If Longhorn is also specified in the new kURL spec and completes its migration process successfully, Rook will be removed to free up resources.
+
+## High Availability
+
+By default, and upon initial installation, MinIO runs as a single replica and relies on the storage it uses being available on every node.
+
+When there is non-distributed storage available on at least three nodes, [EKCO](/docs/add-ons/ekco#minio) will upgrade MinIO to run 6 replicas in a highly-available fashion.
+While this upgrade is in process, MinIO will temporarily go offline.