From 46abdb4a57ccf8feea990996797ecc1d98906622 Mon Sep 17 00:00:00 2001
From: Daryl White <53910321+djwfyi@users.noreply.github.com>
Date: Tue, 17 Jan 2023 15:30:57 -0600
Subject: [PATCH] Adding order of operations for expansion and decommission
 (#705)

- Modifies decommissioning page to mention completing any planned
expansions first.
- Modifies expand deployment page to mention completing before doing any
planned decommssions.
- Minor grammar fixes to expand tenant page.

Closes #702
---
 .../decommission-server-pool.rst                     | 12 ++++++++++++
 .../expand-minio-deployment.rst                      |  2 ++
 .../install-deploy-manage/expand-minio-tenant.rst    |  4 ++--
 3 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/source/operations/install-deploy-manage/decommission-server-pool.rst b/source/operations/install-deploy-manage/decommission-server-pool.rst
index d22d963a..260134d5 100644
--- a/source/operations/install-deploy-manage/decommission-server-pool.rst
+++ b/source/operations/install-deploy-manage/decommission-server-pool.rst
@@ -132,6 +132,18 @@ has a tiering configuration.
 Considerations
 --------------
 
+Replacing a Server Pool
+~~~~~~~~~~~~~~~~~~~~~~~
+
+For hardware upgrade cycles where you replace old pool hardware with a new pool, you should :ref:`add the new pool through expansion <expand-minio-distributed>` before starting the decommissioning of the old pool.
+Adding the new pool first allows the decommission process to transfer objects in a balanced way across all available pools, both existing and new.
+
+Complete any planned :ref:`hardware expansion <expand-minio-distributed>` prior to decommissioning older hardware pools.
+
+Decommissioning requires that a cluster's topology remain stable throughout the pool draining process.
+Do **not** attempt to perform expansion and decommission changes in a single step.
+
+
 Decommissioning Ignores Delete Markers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/source/operations/install-deploy-manage/expand-minio-deployment.rst b/source/operations/install-deploy-manage/expand-minio-deployment.rst
index be922c81..5b2366e8 100644
--- a/source/operations/install-deploy-manage/expand-minio-deployment.rst
+++ b/source/operations/install-deploy-manage/expand-minio-deployment.rst
@@ -256,6 +256,8 @@ those appropriate for your deployment.
 Review the :ref:`expand-minio-distributed-prereqs` before starting this
 procedure.
 
+Complete any planned hardware expansion prior to :ref:`decommissioning older hardware pools <minio-decommissioning>`.
+
 1) Install the MinIO Binary on Each Node in the New Server Pool
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/source/operations/install-deploy-manage/expand-minio-tenant.rst b/source/operations/install-deploy-manage/expand-minio-tenant.rst
index cb1be335..788edbe8 100644
--- a/source/operations/install-deploy-manage/expand-minio-tenant.rst
+++ b/source/operations/install-deploy-manage/expand-minio-tenant.rst
@@ -19,8 +19,8 @@ Prerequisites
 MinIO Kubernetes Operator and Plugin
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-This procedures on this page *requires* a valid installation of the MinIO Kubernetes Operator and assumes the local host has a matching installation of the MinIO Kubernetes Operator.
-This procedure assumes the latest stable Operator and Plugin version |operator-version-stable|.
+This procedure on this page *requires* a valid installation of the MinIO Kubernetes Operator and assumes the local host has a matching installation of the MinIO Kubernetes Operator.
+This procedure assumes the latest stable Operator and Plugin version, |operator-version-stable|.
 
 See :ref:`deploy-operator-kubernetes` for complete documentation on deploying the MinIO Operator.