MinIO is a high performance distributed object storage server, designed for large-scale private cloud infrastructure. MinIO is designed in a cloud-native manner to scale sustainably in multi-tenant environments. Orchestration platforms like Kubernetes provide perfect launchpad for MinIO to scale.

MinIO-Operator brings native MinIO, MCS, and KES support to Kubernetes. MinIO-Operator currently supports following features:

• Kubernetes version v1.17.0 and above for compatibility. MinIO Operator uses k8s/client-go v0.18.0.
• kubectl configured to refer to a Kubernetes cluster.
• Create the required PVs using direct CSI driver.
• Optional: kustomize installed as explained here.

To start MinIO-Operator with default configuration, use the minio-operator.yaml file.

kubectl apply -f https://raw.githubusercontent.com/minio/minio-operator/master/minio-operator.yaml

Advanced users can leverage kustomize to customize operator configuration

git clone https://github.com/minio/minio-operator
kustomize build | kubectl apply -f -

Once MinIO-Operator deployment is running, you can create MinIO instances using the below command

kubectl apply -f https://raw.githubusercontent.com/minio/minio-operator/master/examples/tenant.yaml

Add an external service in Tenant definition to enable Service based access to the Tenant pods. Refer the example here for details on how to setup service based access for Tenant pods.

These variables may be passed to operator Deployment in order to modify some of its parameters

• MinIO Erasure Code QuickStart Guide
• Use mc with MinIO Server
• Use aws-cli with MinIO Server
• The MinIO documentation website
• Expose MinIO via Istio: Istio >= 1.4 has support for headless Services, so instead of creating an explicit Service for the created MinIO instance, you can also directly target the headless Service that is created by the operator. Use Istio Ingress Gateway to configure Istio to expose the MinIO service outside of the service mesh.