From d2e88996859295e56fa1bd6b373738c4094490ef Mon Sep 17 00:00:00 2001 From: Cesar Celis Hernandez Date: Fri, 11 Aug 2023 08:29:56 -0600 Subject: [PATCH] Rephrasing the Operator Support (#948) ### Objective: To rephrase the Operator Support accordingly for single node single drive configurations. --------- Co-authored-by: Ravind Kumar --- .../install-deploy-manage/deploy-minio-tenant.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/source/operations/install-deploy-manage/deploy-minio-tenant.rst b/source/operations/install-deploy-manage/deploy-minio-tenant.rst index e4d874c2..3894ce04 100644 --- a/source/operations/install-deploy-manage/deploy-minio-tenant.rst +++ b/source/operations/install-deploy-manage/deploy-minio-tenant.rst @@ -33,8 +33,13 @@ Deploy a MinIO Tenant :class: no-scaled-link :alt: MinIO Operator Console -The MinIO Operator supports only the Distributed (Multi-Node Multi-Drive) MinIO topology. -You can use basic Kubernetes YAML resource definitions to deploy Single-Node Single-Drive and Single-Node Multi-Drive topologies for local testing and evaluation as necessary. + +The MinIO Operator Console is designed with deploying multi-node distributed MinIO Deployments. + +Deploying Single-Node topologies requires additional configurations not covered in this documentation. +You can alternatively use a simple Kubernetes YAML object to describe a Single-Node topology for local testing and evaluation as necessary. + +MinIO does not recommend nor support single-node deployment topologies for production environments. The Operator Console provides a rich user interface for deploying and managing MinIO Tenants on Kubernetes infrastructure. Installing the MinIO :ref:`Kubernetes Operator ` automatically installs and configures the Operator Console.