You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Harshavardhana 3ca9f5ffa3 Update yaml files to latest version RELEASE.2020-03-14T02-21-58Z 5 years ago
..
README.md
k8s-yaml.md
minio-distributed-daemonset.yaml Update yaml files to latest version RELEASE.2020-03-14T02-21-58Z 5 years ago
minio-distributed-headless-service.yaml doc: Update Kubernetes examples to use Readiness Checks (#8727) 5 years ago
minio-distributed-service.yaml
minio-distributed-statefulset.yaml Update yaml files to latest version RELEASE.2020-03-14T02-21-58Z 5 years ago
minio-gcs-gateway-deployment.yaml Update yaml files to latest version RELEASE.2020-03-14T02-21-58Z 5 years ago
minio-gcs-gateway-service.yaml
minio-standalone-deployment.yaml Update yaml files to latest version RELEASE.2020-03-14T02-21-58Z 5 years ago
minio-standalone-pvc.yaml
minio-standalone-service.yaml Cleanup Kubernetes documentation (#6678) 6 years ago

README.md

Deploy MinIO on Kubernetes Slack Go Report Card Docker Pulls

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 cloud-native environment to deploy and scale MinIO.

MinIO Deployment on Kubernetes

There are multiple options to deploy MinIO on Kubernetes:

  • MinIO-Operator: Operator offers seamless way to create and update highly available distributed MinIO clusters. Refer MinIO Operator documentation for more details.

  • Helm Chart: MinIO Helm Chart offers customizable and easy MinIO deployment with a single command. Refer MinIO Helm Chart documentation for more details.

  • YAML File: MinIO can be deployed with YAML files via kubectl. Refer to the MinIO YAML file documentation for more details.

Monitoring MinIO in Kubernetes

MinIO server exposes un-authenticated readiness and liveness endpoints so Kubernetes can natively identify unhealthy MinIO containers. MinIO also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their MinIO deployments.

Note : Readiness check is not allowed in distributed MinIO deployment. This is because Kubernetes doesn't allow any traffic to containers whose Readiness checks fail, and in a distributed setup, MinIO server can't respond to Readiness checks until all the nodes are reachable. So, Liveness checks are recommended native Kubernetes monitoring approach for distributed MinIO StatefulSets. Read more about Kubernetes recommendations for container probes.

Explore Further