From 9e7388cc9f9460855722506af8ded414d93b6ec6 Mon Sep 17 00:00:00 2001
From: Daryl White <53910321+djwfyi@users.noreply.github.com>
Date: Mon, 13 Jan 2025 11:28:11 -0500
Subject: [PATCH] Bug fixes for two issues (#1392)

## Tenant Namespaces

Adds information for unique tenant namespaces.

Closes #1391

## Changing erasure code parity

Adds information about changes to erasure code to MNMD deploys.

Closes #1365
---
 .../deploy-minio-multi-node-multi-drive.rst                 | 4 +++-
 .../install-deploy-manage/deploy-minio-tenant-helm.rst      | 6 ++++++
 .../install-deploy-manage/deploy-minio-tenant.rst           | 6 ++++++
 3 files changed, 15 insertions(+), 1 deletion(-)

diff --git a/source/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst b/source/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst
index ac146673..52b6771c 100644
--- a/source/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst
+++ b/source/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst
@@ -141,7 +141,9 @@ Consider using the MinIO `Erasure Code Calculator <https://min.io/product/erasur
 
 .. important::
 
-   While you can change erasure parity settings at any time, objects written with a given parity do **not** automatically update to the new parity settings.
+   While you can change erasure parity settings at any time, objects written with a given parity do **not** update to the new parity settings.
+   MinIO only applies the changed parity to newly written objects.
+   Existing objects retain the parity value in place at the time of their creation.
 
 Capacity-Based Planning
 ~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/source/operations/install-deploy-manage/deploy-minio-tenant-helm.rst b/source/operations/install-deploy-manage/deploy-minio-tenant-helm.rst
index b9e527bc..c0d99573 100644
--- a/source/operations/install-deploy-manage/deploy-minio-tenant-helm.rst
+++ b/source/operations/install-deploy-manage/deploy-minio-tenant-helm.rst
@@ -48,6 +48,12 @@ For more about Tenant installation requirements, including supported Kubernetes
 This procedure assumes familiarity the with referenced Kubernetes concepts and utilities.
 While this documentation may provide guidance for configuring or deploying Kubernetes-related resources on a best-effort basis, it is not a replacement for the official :kube-docs:`Kubernetes Documentation <>`.
 
+Namespace
+~~~~~~~~~
+
+The tenant must use its own namespace and cannot share a namespace with another tenant.
+In addition, MinIO strongly recommends using a dedicated namespace for the tenant with no other applications running in the namespace.
+
 .. _deploy-tenant-helm-repo:
 
 Deploy a MinIO Tenant using Helm Charts
diff --git a/source/operations/install-deploy-manage/deploy-minio-tenant.rst b/source/operations/install-deploy-manage/deploy-minio-tenant.rst
index b6ca8a04..a9348b2c 100644
--- a/source/operations/install-deploy-manage/deploy-minio-tenant.rst
+++ b/source/operations/install-deploy-manage/deploy-minio-tenant.rst
@@ -200,6 +200,12 @@ Persistent Volumes
    MinIO strongly recommends SSD-backed disk types for best performance.
    For more information on AKS disk types, see :azure-docs:`Azure disk types <virtual-machines/disk-types>`.
 
+Namespace
+~~~~~~~~~
+
+The tenant must use its own namespace and cannot share a namespace with another tenant.
+In addition, MinIO strongly recommends using a dedicated namespace for the tenant with no other applications running in the namespace.
+
 .. _minio-k8s-deploy-minio-tenant-security:
 
 Deploy a MinIO Tenant using Kustomize