The content of these pages are under active development and may change at any time. Thank you for your patience.

Manage a MinIO Tenant

Overview

This page documents several common procedures for managing an existing MinIO tenant. You can view the list of tenants at any time from the MinIO plugin for vSphere.

MinIO Tenant View

Select the VCF cluster and open the Configure tab. Navigate to the MinIO section and click Tenants to view all MinIO tenants deployed in that cluster.

Expand a MinIO Tenant

Zone expansion increases the total usable storage capacity of the MinIO tenant. Each zone consists of an independent pool of hosts and their locally-attached storage. MinIO presents all zones in the tenant as a single storage resource for applications to access.

Prerequisites

MinIO creates new Tenant pods on available ESXi hosts in the cluster. Each ESXi host must have sufficient compute, memory, and direct-attached storage to support each pod provisioned as part of the new tenant zone. MinIO requires one available ESXi host for each MinIO server pod deployed as part of the zone.

All zones in a MinIO tenant use the same storage policy. Ensure each ESXi host’s locally attached drives are included in the storage policy used by the MinIO tenant.

1) Open the Add New Zone Modal

From the vCenter interface, select the cluster in which the MinIO tenant you want to expand is deployed. Click the Configure tab, then open the MinIO section and select Tenants to open the MinIO Tenants view.

MinIO View All Tenants

Click the radio button next to the tenant you want to expand and select Details to open the Tenant view.

From the Tenant view, locate the Zones section and click Add to open the Add New Zone modal.

MinIO View All Tenants

2) Complete the Add New Zone Modal

MinIO View All Tenants

The Add New Zone modal displays the following fields:

Number of Nodes

Specify the number of nodes to create for the new MinIO tenant zone.

Zone size

Specify the total amount of storage for the new MinIO tenant zone.

Memory per Node [Gi]

The amount of memory to allocate to each MinIO object storage pod in the zone.

The modal displays the summary of the new zone below the text inputs.

Nodes

The number of nodes in the zone.

Volumes per Node

The number of Persistent Volume Claims (PVC) that MinIO generates per node in the tenant zone.

Disk Size

The requested storage capacity for each PVC that MinIO generates for the tenant zone.

Total Number of Volumes

The total number of PVC that MinIO generates for the Tenant.

Click OK to add the new Zone.

3) Monitor Zone Creation

You can view the progress of the zone creation from the Tenant view.

MinIO Tenant with Multiple Zones

The tenant Storage and Health may display warnings while MinIO provisions the pods, Persistent Volume Claims, and Persistent Volumes required to create the zone.

Update a MinIO Tenant

The MinIO plugin supports upgrading the MinIO tenant through the vCenter interface. You can update the following components:

Updating the MinIO tenant requires restarting multiple pods simultaneously. The update interrupts ongoing API operations until complete. Consider performing the update during a maintenance period to minimize disruption to applications.

Important

You cannot downgrade the MinIO Object Storage server used by a tenant once deployed. Use a staging or development tenant for testing the desired MinIO server version before making upgrades in a production tenant.

1) Open the Update MinIO Version Modal

From the vCenter interface, select the cluster in which the MinIO tenant you want to expand is deployed. Click the Configure tab, then open the MinIO section and select Tenants to open the MinIO Tenants view.

MinIO View All Tenants

Click the radio button next to the tenant you want to expand and select Details to open the Tenant view.

From the Tenant view, click the pencil icon on the Version row to open the Update MinIO Version modal.

MinIO Tenant Upgrade

2) Complete the Update MinIO Version Modal

MinIO Tenant Update Modal

The modal displays the following fields:

MinIO’s Image

The Docker image to use for updating the MinIO tenant. The MinIO plugin uses the minio/minio image repository hosted at hub.docker.com by default.

Leave blank to use the latest stable minio image.

Console’s Image

The Docker image to use for updating the MinIO Console deployed as part of the MinIO tenant. The MinIO plugin uses the minio/console image repository hosted at hub.docker.com by default.

Leave blank to use the latest stable console image.

Set Custom Image Registry

Enables using a private Docker repository for retrieving Docker images when updating the MinIO tenant. Enter the Endpoint of the repository along with the Username and Password required to access the repository.

Enable prometheus integration

Enables annotations that allow Prometheus to scrape the MinIO tenant using the Kubernetes REST API. See the Prometheus documenation for more information.

Click OK to begin the update. MinIO updates all pods in the tenant simultaneously. The tenant may have a brief period of downtime during the update process.