MinIO for VMware Cloud Foundation 4.2¶
Welcome to the MinIO Object Storage documentation for VMware Cloud Foundation 4.2.
MinIO is a Kubernetes-native object store designed to provide high performance with an S3-compatible API. VCF 4.2 includes MinIO’s vCenter plugin for provisioning multi-tenant object storage on VMware Tanzu Kubernetes infrastructure. See MinIO Object Storage on VMware Cloud Foundation with Tanzu for additional information.
This documentation assumes familiarity with all referenced Kubernetes and VMware concepts, utilities, and procedures. While this documentation may provide guidance for configuring or deploying non-MinIO resources on a best-effort basis, it is not a replacement for the official Kubernetes Documentation or VMware Documentation.
This documentation summarizes core features and functionality of MinIO Object Storage. For more complete documentation, see the documentation for MinIO Object Storage for Baremetal.
Use the Deploy a MinIO Tenant guide to create a MinIO tenant on using VMware vCenter and the MinIO plugin.
For managing an existing MinIO tenant, see Manage a MinIO Tenant.
Inside a MinIO Tenant¶
Each tenant consists of the following core components:
A set of MinIO server pods which pool their drives for supporting object storage and retrieval requests. A MinIO tenant can have an unlimited number of Zones, where each new Zone expands the total available storage on the cluster.
The Zone terminology is unique to MinIO on VCF and is equivalent in usage and behavior to Server Pools or Pools as referenced in other MinIO documentation properties.
- Erasure Set
A set of drives that support MinIO Erasure Coding. Erasure coding provides high availability, reliability, and redundancy of data stored on the tenant.
Each Zone has at least one Erasure Set, where MinIO automatically calculates the optimal Erasure Set size for the zone. See Erasure Coding for more information.