1
0
mirror of https://github.com/minio/docs.git synced 2025-07-30 07:03:26 +03:00

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
This commit is contained in:
Daryl White
2025-01-13 11:28:11 -05:00
committed by GitHub
parent fff6e87c03
commit 9e7388cc9f
3 changed files with 15 additions and 1 deletions

View File

@ -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
~~~~~~~~~~~~~~~~~~~~~~~

View File

@ -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

View File

@ -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