docs/source/operations/install-deploy-manage/deploy-minio-tenant.rst

Deploy a MinIO Tenant

minio

Table of Contents

openshift

This procedure documents deploying a MinIO Tenant through OpenShift 4.7+ using the OpenShift Web Console and the MinIO Kubernetes Operator.

k8s and not openshift

This procedure documents deploying a MinIO Tenant onto a stock Kubernetes cluster using the MinIO Operator Console.

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 Kubernetes Operator <deploy-operator-kubernetes> automatically installs and configures the Operator Console.

This documentation assumes familiarity with all referenced Kubernetes concepts, utilities, and procedures. 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 Kubernetes Documentation <>.

Prerequisites

MinIO Kubernetes Operator and Plugin

The 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 .

See deploy-operator-kubernetes for complete documentation on deploying the MinIO Operator.

k8s and not openshift

openshift

k8s and not (openshift or eks or gke or aks)

Kubernetes Version 1.19.0

Starting with v4.0.0, the MinIO Operator requires Kubernetes 1.19.0 and later. The Kubernetes infrastructure and the kubectl CLI tool must have the same version of 1.19.0+.

This procedure assumes the host machine has kubectl installed and configured with access to the target Kubernetes cluster. The host machine must have access to a web browser application.

openshift

OpenShift 4.7+ and oc CLI Tool

This procedure assumes installation of the MinIO Operator using the OpenShift 4.7+ and the OpenShift OperatorHub.

This procedure assumes your local machine has the OpenShift oc CLI tool installed and configured for access to the OpenShift Cluster. Download and Install <cli_reference/openshift_cli/getting-started-cli.html> the OpenShift CLI (command-line interface) oc for use in this procedure.

See deploy-operator-openshift for more complete instructions.

openshift

Check Security Context Constraints

The MinIO Operator deploys pods using the following default Security Context <tasks/configure-pod-container/security-context/> per pod:

securityContext:
  runAsUser: 1000
  runAsGroup: 1000
  runAsNonRoot: true
  fsGroup: 1000

Certain OpenShift Security Context Constraints </authentication/managing-security-context-constraints.html> limit the allowed UID or GID for a pod such that MinIO cannot deploy the Tenant successfully. Ensure that the Project in which the Operator deploys the Tenant has sufficient SCC settings that allow the default pod security context. You can alternatively modify the tenant security context settings during deployment.

The following command returns the optimal value for the securityContext:

oc get namespace <namespace> \
-o=jsonpath='{.metadata.annotations.openshift\.io/sa\.scc\.supplemental-groups}{"\n"}'

The command returns output similar to the following:

1056560000/10000

Take note of this value before the slash for use in this procedure.

gke

GKE Cluster with Compute Engine Nodes

This procedure assumes an existing GKE (Google Kubernetes Engine) cluster with a MinIO Operator installation and at least four Compute Engine nodes. The Compute Engine nodes should have matching machine types and configurations to ensure predictable performance with MinIO.

MinIO provides hardware guidelines <deploy-minio-distributed-recommendations> for selecting the appropriate Compute Engine instance class and size. MinIO strongly recommends selecting instances with support for local SSDs and at least 25Gbps egress bandwidth as a baseline for performance.

For more complete information on the available Compute Engine and Persistent Storage resources, see Machine families resources and comparison guide <general-purpose-machines> and Persistent disks <disks>.

eks

EKS Cluster with EBS-Optimized EC2 Nodes

This procedure assumes an existing EKS (Elastic Kubernetes Service) cluster with at least four EC2 nodes. The EC2 nodes should have matching machine types and configurations to ensure predictable performance with MinIO.

MinIO provides hardware guidelines <deploy-minio-distributed-recommendations> for selecting the appropriate EC2 instance class and size. MinIO strongly recommends selecting EBS-optimized instances with at least 25Gbps Network bandwidth as a baseline for performance.

For more complete information on the available EC2 and EBS resources, see EC2 Instance Types and EBS Volume Types. customers should reach out to MinIO engineering as part of architecture planning for assistance in selecting the optimal instance and volume types for the target workload and performance goals.

aks

AKS Cluster with Azure Virtual Machines

This procedure assumes an existing AKS (Azure Kubernetes Service) cluster with at least four Azure virtual machines (VM). The Azure VMs should have matching machine types and configurations to ensure predictable performance with MinIO.

MinIO provides hardware guidelines <deploy-minio-distributed-recommendations> for selecting the appropriate EC2 instance class and size. MinIO strongly recommends selecting VM instances with support for Premium SSDs and at least 25Gbps Network bandwidth as a baseline for performance.

For more complete information on Azure Virtual Machine types and Storage resources, see Sizes for virtual machines in Azure <virtual-machines/sizes> and Azure managed disk types <virtual-machines/disks-types>

Persistent Volumes

not eks

MinIO can use any Kubernetes Persistent Volume (PV) <concepts/storage/persistent-volumes> that supports the ReadWriteOnce <concepts/storage/persistent-volumes/#access-modes> access mode. MinIO's consistency guarantees require the exclusive storage access that ReadWriteOnce provides. Additionally, MinIO recommends setting a reclaim policy of Retain for the PVC StorageClass <concepts/storage/storage-classes>.

For Kubernetes clusters where nodes have Direct Attached Storage, MinIO strongly recommends using the DirectPV CSI driver. DirectPV provides a distributed persistent volume manager that can discover, format, mount, schedule, and monitor drives across Kubernetes nodes. DirectPV addresses the limitations of manually provisioning and monitoring local persistent volumes <concepts/storage/volumes/#local>.

eks

MinIO Tenants on EKS must use the EBS CSI Driver <kubernetes-sigs/aws-ebs-csi-driver> to provision the necessary underlying persistent volumes. MinIO strongly recommends using SSD-backed EBS volumes for best performance. MinIO strongly recommends deploying EBS-based PVs with the XFS filesystem. Create a StorageClass for the MinIO EBS PVs and set the csi.storage.k8s.io/fstype parameter to xfs . For more information on EBS resources, see EBS Volume Types. For more information on StorageClass Parameters, see StorageClass Parameters.

gke

MinIO Tenants on GKE should use the Compute Engine Persistent Disk CSI Driver <how-to/persistent-volumes/gce-pd-csi-driver> to provision the necessary underlying persistent volumes. MinIO strongly recommends SSD-backed disk types for best performance. For more information on GKE disk types, see Persistent Disks <disks>.

aks

MinIO Tenants on AKS should use the Azure Disks CSI driver <azure-disk-csi> to provision the necessary underlying persistent volumes. MinIO strongly recommends SSD-backed disk types for best performance. For more information on AKS disk types, see Azure disk types <virtual-machines/disk-types>.

Deploy a Tenant using the MinIO Operator Console

To deploy a tenant from the MinIO Operator Console, complete the following steps in order:

create-tenant-access-minio-operator-console

create-tenant-complete-tenant-setup

create-tenant-configure-section

create-tenant-images-section

create-tenant-pod-placement-section

create-tenant-identity-provider-section

create-tenant-security-section

create-tenant-encryption-section

minio-tenant-audit-logging-settings

minio-tenant-monitoring-settings

create-tenant-deploy-view-tenant

create-tenant-connect-tenant

1) Access the MinIO Operator Console

Open your browser to the specified URL and enter the JWT Token into the login page. You should see the Tenants page:

Click the + Create Tenant to start creating a MinIO Tenant.

2) Complete the Tenant Setup

The Setup pane displays core configuration settings for the MinIO Tenant.

Settings marked with an asterisk * are required:

Field	Description
Name	The name of the MinIO Tenant
Namespace	The Kubernetes Namespace in which to deploy the tenant. You can create the namespace by selecting the plus + icon if it does not exist. The Operator supports at most one MinIO Tenant per namespace.
Storage Class	not eks Specify the Kubernetes Storage Class the Operator uses when generating Persistent Volume Claims for the Tenant. Ensure the specified storage class has sufficient available Persistent Volume resources to match each generated Persistent Volume Claim. eks Specify the EBS volume type to use for this tenant. The following list is populated based on the AWS EBS CSI driver list of supported EBS volume types <kubernetes-sigs/aws-ebs-csi-driver/blob/master/docs/parameters.md>: gp3 (General Purpose SSD) gp2 (General Purpose SSD) io2 (Provisioned IOPS SSD) io1 (Provisioned IOPS SSD) st1 (Throughput Optimized HDD) sc1 (Cold Storage HDD) gke Specify the GKE persistent disk type to use for this tenant. The GKE CSI Driver <how-to/persistent-volumes/gce-pd-csi-driver> provides the following storage classes by default: standard-rwo (Balanced Persistent SSD) premium-rwo (Performance Persistent SSD) You can create additional StorageClasses to represent other supported persistent disk types. See Create a Storage Class <how-to/persistent-volumes/gce-pd-csi-driver#create_a_storageclass> for more information. aks Specify the AKS persistent disk type to use for this tenant. The AKS CSI Driver <azure-disk-csi> provides the following storage classes by default: managed-csi (Standard SSD) managed-csi-premium (Premium SSD) You can create additional Storage Classes to represent other supported persistent disk types. See Create a custom storage class <https://learn.microsoft.com/en-us/azure/aks/azure-disk-csi#create-a-custom-storage-class> for more information.
Number of Servers	The total number of MinIO server pods to deploy in the Tenant. The Operator enforces a minimum of four server pods per tenant. The Operator by default uses pod anti-affinity, such that the Kubernetes cluster must have at least one worker node per MinIO server pod. Use the Pod Placement pane to modify the pod scheduling settings for the Tenant.
Number of Drives per Server	The number of storage volumes (Persistent Volume Claims) the Operator requests per Server. The Operator displays the Total Volumes under the Resource Allocation section. The Operator generates an equal number of PVC plus two for supporting Tenant services (Metrics and Log Search). not eks The specified Storage Class must correspond to a set of Persistent Volumes sufficient in number to match each generated PVC. eks For deployments using the EBS CSI driver, the Operator provisions Persistent Volume Claims which result in the creation of EBS volumes of the specified Storage Class equal to Number of Drives per Server X Number of Servers. gke For deployments using the GKE CSI driver, the Operator provisions Persistent Volume Claims which result in the creation of GCP Disks of the specified Storage Class equal to Number of Drives per Server X Number of Servers. aks For deployments using the AKS CSI Driver, the Operator provisions Persistent Volume Claims which result in the creation of Azure Disks of the specified Storage Class equal to Number of Drives per Server X Number of Servers.
Total Size	The total raw storage size for the Tenant. Specify both the total storage size and the Unit of that storage. All storage units are in SI values, e.g. Gi = GiB = 10243 bytes. The Operator displays the Drive Capacity under theResource Allocation section. The Operator sets this value as the requested storage capacity in each generated PVC. The specified Storage Class must correspond to a set of Persistent Volumes sufficient in capacity to match each generated PVC.
Memory per Node [Gi]	Specify the total amount of memory (RAM) to allocate per MinIO server pod. See minio-hardware-checklist-memory for guidance on setting this value. The Kubernetes cluster must have worker nodes with sufficient free RAM to match the pod request.
Erasure Code Parity	The Erasure Code Parity to set for the deployment. The Operator displays the selected parity and its effect on the deployment under the Erasure Code Configuration section. Erasure Code parity defines the overall resiliency and availability of data on the cluster. Higher parity values increase tolerance to drive or node failure at the cost of total storage. See minio-erasure-coding for more complete documentation.

Select Create to create the Tenant using the current configuration. While all subsequent sections are optional, MinIO recommends reviewing them prior to deploying the Tenant.

3) The Configure Section

The Configure section displays optional configuration settings for the MinIO Tenant and its supporting services.

Field	Description
Expose MinIO Service	The MinIO Operator by default directs the MinIO Tenant services to request an externally accessible IP address from the Kubernetes cluster Load Balancer if one is available to access the tenant. eks If your EKS cluster includes the AWS Load Balancer Controller add-on <eks/latest/userguide/aws-load-balancer-controller.html>, enabling this setting directs the load balancer to assign an address to the Tenant services. Other load balancers may function similarly depending on their configuration. not eks Your Kubernetes distributions may include a load balancer that can respond to these requests. Installation and configuration of load balancers is out of the scope of this documentation.
Expose Console Service	Select whether the Tenant should request an IP address from the Load Balancer to access the Tenant's Console. eks If your EKS cluster includes the AWS Load Balancer Controller add-on <eks/latest/userguide/aws-load-balancer-controller.html>, enabling this setting directs the load balancer to assign an address to the Tenant services. Other load balancers may function similarly depending on their configuration. not eks Your Kubernetes distributions may include a load balancer that can respond to these requests. Installation and configuration of load balancers is out of the scope of this documentation.
Set Custom Domains	Toggle on to customize the domains allowed to access the tenant's console and other tenant services.
Security Context	The MinIO Operator sets the Kubernetes Security Context for pods to a default of 1000 for User, Group, and FsGroup. The FSGroupChangePolicy defaults to Always. MinIO does not run the pod using the root user. You can modify the Security Context to direct MinIO to run using a different User, Group,FsGroup ID, and FSGroupChangePolicy. You can also direct MinIO to run as the Root user. openshift Important If your OpenShift cluster enforces Security Context Constraints </authentication/managing-security-context-constraints.html> , ensure you set the Tenant constraints appropriately such that pods can start and run normally.
Custom Runtime Configurations	Toggle on to customize the Runtime Class <concepts/containers/runtime-class/> for the tenant to use.
Additional Environment Variables	Enter any additional the key:value pairs to use as environment variables for the tenant.

4) The Images Section

The Images section displays container image settings used by the MinIO Tenant.

Field	Description
MinIO's Image	The container image to use for the MinIO Server. See the MinIO Quay or the MinIO DockerHub repositories for a list of valid tags.
Log Search API's Image	The container image to use for MinIO Log Search API.
KES Image	The container image to use for MinIO KES <kes>.
Log Search Postgres Image Log Search Postgres Init Image	The container images to use for starting the PostgreSQL service supporting the Log Search API
Prometheus Image Prometheus Sidecar Image Prometheus Init Image	The container images to use for starting the Prometheus service supporting the Log Search API.

5) The Pod Placement Section

The Pod Placement section displays pod scheduler settings for the MinIO Tenant.

Field	Description
None	Disables pod scheduling constraints for the tenant. This allows Kubernetes to schedule multiple Tenant pods onto the same node. This may decrease resiliency, as a single Kubernetes worker can host multiple MinIO pods. If that worker is down or lost, objects may also be unavailable or lost. Consider using this setting only in early development or sandbox environments with a limited number of worker nodes.
Default (Pod Anti-Affinity)	Directs the Operator to set anti-affinity settings such that no Kubernetes worker can host more than one MinIO server pod for this Tenant.
Node Selector	Directs the operator to set a Node Selector such that pods only deploy onto Kubernetes workers whose labels match the selector.

6) The Identity Provider Section

The Identity Provider section displays the Identity Provider <minio-authentication-and-identity-management> settings for the MinIO Tenant. This includes configuring an external IDP such as OpenID <minio-external-identity-management-openid> or Active Directory / LDAP <minio-external-identity-management-ad-ldap>.

Field	Description
Built-In	Configure additional internal MinIO users for the Operator to create as part of deploying the Tenant.
OpenID	Configure an OpenID Connect-compatible service as an external Identity Provider (e.g. Keycloak, Okta, Google, Facebook, Dex) to manage MinIO users.
Active Directory	Configure an Active Directory or OpenLDAP service as the external Identity Provider to manage MinIO users.

7) The Security Section

The Security section displays TLS certificate settings for the MinIO Tenant.

Field	Description
Enable TLS	Enable or disable TLS for the MinIO Tenant.
Enable AutoCert	Directs the Operator to generate Certificate Signing Requests for submission to the Kubernetes TLS API. The MinIO Tenant uses the generated certificates for enabling and establishing TLS connections.
Custom Certificates	When enabled, you can upload custom TLS certificates for MinIO to use for server and client credentials. MinIO supports Server Name Indication (SNI) such that the Tenant can select the appropriate TLS certificate based on the request hostname and the certificate Subject Alternative Name. MinIO also supports uploading Certificate Authority certificates for validating client certificates minted by that CA.

Supported Secret Types

Console 0.23.1

A message displays under the certificate with the date of expiration and length of time until expiration.

The message adjusts depending on the length of time to expiration:

• More than 30 days, the message text displays in gray.
• Within 30 days, the message text changes to orange.
• Within 10 days, the message text changes to red.
• Within 24 hours, the message displays as an hour and minute countdown in red text.
• After expiration, the message displays as EXPIRED.

1) The Encryption Section

The Encryption section displays the Server-Side Encryption (SSE) <minio-sse> settings for the MinIO Tenant.

Enabling SSE also creates MinIO Key Encryption Service <kes> pods in the Tenant to facilitate SSE operations.

Field	Description
Vault	Configure Hashicorp Vault as the external KMS for storing root encryption keys. See minio-sse-vault for guidance on the displayed fields.
AWS	Configure AWS Secrets Manager as the external KMS for storing root encryption keys. See minio-sse-aws for guidance on the displayed fields.
GCP	Configure Google Cloud Platform Secret Manager as the external KMS for storing root encryption keys. See minio-sse-gcp for guidance on the displayed fields.
Azure	Configure Azure Key Vault as the external KMS for storing root encryption keys. See minio-sse-azure for guidance on the displayed fields.

9) Audit Log Settings

Console 0.23.1 and Operator 5.0.0

New tenants have Audit Logs Disabled by default.

Field	Description
Log Search Storage Class	Select the storage class and requested capacity associated to the PVC generated to support audit logging.
Storage Size	Specify the size of storage to make available for audit logging.
SecurityContext for LogSearch	The MinIO Operator deploys a Log Search service (SQL Database and Log Search API) to support Audit Log search in the MinIO Tenant Console. You can modify the Security Context to run the associated pod commands using a different User, Group, FsGroup, or FSGroupChangePolicy. You can also direct the pod to not run commands as the Root user.
SecurityContext for PostgreSQL	The MinIO Operator deploys a PostgreSQL database to support logging services. You can modify the Security Context to run the associated pod commands using a different User, Group, FsGroup, or FSGroupChangePolicy. You can also direct the pod to not run commands as the Root user. You can also modify the storage class and requested capacity associated to the PVC generated to support the Prometheus service.

10) Monitoring Settings

Console 0.23.1 and Operator 5.0.0

New tenants have monitoring Disabled by default.

Field	Description
Storage Class	Select the storage class and requested capacity associated to the PVC generated to support Prometheus.
Storage Size	Specify the size of storage to make available for Prometheus.
SecurityContext	The MinIO Operator assigns this Security Context for the Prometheus pod. You can modify the Security Context to run the associated pod commands using a different User, Group, FsGroup, or FSGroupChangePolicy. You can also direct the pod to not run commands as the Root user.

11) Deploy and View the Tenant

Select Create at any time to begin the deployment process. The MinIO Operator displays the root user credentials once as part of deploying the Tenant. Copy these credentials to a secure location.

You can monitor the Tenant creation process from the Tenants view. The State column updates throughout the deployment process.

Tenant deployment can take several minutes to complete. Once the State reads as Initialized, click the Tenant to view its details.

Each tab provides additional details or configuration options for the MinIO Tenant.

• METRICS - Displays metrics collected from the MinIO Tenant.
• SECURITY - Provides TLS-related configuration options.
• POOLS - Supports expanding the tenant by adding more Server Pools.
• LICENSE - Enter your SUBNET license.

12) Connect to the Tenant

The MinIO Operator creates services for the MinIO Tenant.

openshift

Use the oc get svc -n TENANT-PROJECT command to review the deployed services:

oc get svc -n minio-tenant-1

k8s and not openshift

Use the kubectl get svc -n NAMESPACE command to review the deployed services:

kubectl get svc -n minio-tenant-1

NAME                               TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
minio                              LoadBalancer   10.97.114.60     <pending>     443:30979/TCP    2d3h
minio-tenant-1-console             LoadBalancer   10.106.103.247   <pending>     9443:32095/TCP   2d3h
minio-tenant-1-hl                  ClusterIP      None             <none>        9000/TCP         2d3h
minio-tenant-1-log-hl-svc          ClusterIP      None             <none>        5432/TCP         2d3h
minio-tenant-1-log-search-api      ClusterIP      10.103.5.235     <none>        8080/TCP         2d3h
minio-tenant-1-prometheus-hl-svc   ClusterIP      None             <none>        9090/TCP         7h39m

• The minio service corresponds to the MinIO Tenant service. Applications should use this service for performing operations against the MinIO Tenant.
• The *-console service corresponds to the MinIO Console <console>. Administrators should use this service for accessing the MinIO Console and performing administrative operations on the MinIO Tenant.

The remaining services support Tenant operations and are not intended for consumption by users or administrators.

By default each service is visible only within the Kubernetes cluster. Applications deployed inside the cluster can access the services using the CLUSTER-IP.

Applications external to the Kubernetes cluster can access the services using the EXTERNAL-IP. This value is only populated for Kubernetes clusters configured for Ingress or a similar network access service. Kubernetes provides multiple options for configuring external access to services.

k8s and not openshift

See the Kubernetes documentation on Publishing Services (ServiceTypes) <concepts/services-networking/service/#publishing-services-service-types> and Ingress <concepts/services-networking/ingress/> for more complete information on configuring external access to services.

openshift

See the OpenShift documentation on Route or Ingress <networking/understanding-networking.html#nw-ne-comparing-ingress-route_understanding-networking> for more complete information on configuring external access to services.

openshift

k8s and not (openshift or eks)

/operations/install-deploy-manage/deploy-minio-tenant-helm