MinIO Operator Console

Table of Contents

Tenant Management
Persistent Volume Management

The Operator Console provides a rich user interface for deploying and managing MinIO Tenants on Kubernetes infrastructure. Installing the MinIO Kubernetes Operator automatically installs and configures the Operator Console.

This page summarizes the functions available with the MinIO Operator Console.

Use the kubectl minio proxy command to temporarily forward traffic between the local host machine and the MinIO Operator Console:

kubectl minio proxy

The command returns output similar to the following:

Starting port forward of the Console UI.

To connect open a browser and go to http://localhost:9090

Current JWT to login: TOKEN

Open your browser to the specified URL and enter the JWT Token into the login page.

Tenant Management

The MinIO Operator Console supports deploying, managing, and monitoring MinIO Tenants on the Kubernetes cluster.

You can deploy a MinIO Tenant through the Operator Console.

The Operator Console automatically detects any MinIO Tenants deployed on the cluster, whether provisioned through the Operator Console or through the MinIO Kubernetes Plugin.

For each listed tenant, select MANAGE to open an in-browser view of that tenant’s MinIO Console. You can use this view to directly manage the tenant through the Operator UI.

Select VIEW to view the Tenant details and configurations. You can modify, expand, upgrade, and delete the Tenant from this view.

Persistent Volume Management

The MinIO Operator Console includes an interface for managing storage volumes and volume claims associated to MinIO Tenants.

The Volumes tab displays all Persistent Volume Claims generated for Tenants managed by the MinIO Operator.
The Drives tab displays any locally attached drives that are currently managed or eligible for management by MinIO DirectCSI.

MinIO DirectCSI supports dynamic provisioning of persistent volumes from locally-attached storage. DirectCSI manages allocation of volumes based on storage capacity and schedules pods to run on nodes which have the most available capacity. See the DirectCSI Documentation for installation and configuration instructions.

You can use DirectCSI for any Kubernetes service that can take advantage of dynamically provisioned locally-attached storage by specifying the direct-csi-min-io StorageClass as part of the Persistent Volume Claim.