minio/docs/orchestration
Nitish Tiwari 496fba3e9a
Return 200 OK for liveness checks while distributed cluster starts (#8176)
With this PR, liveness check responds with 200 OK with "server-not-
initialized" header while objectLayer gets initialized. The header
is removed as objectLayer is initialized. This is to allow
MinIO distributed cluster to get started when running on an
orchestration platforms like Docker Swarm.

This PR also updates sample Swarm yaml files to use correct values
for healthcheck fields.

Fixes #8140
2019-09-05 14:50:56 +05:30
..
dcos Removes the incorrect coverage badge from the docs (#7651) 2019-05-16 12:11:49 +05:30
docker-compose Return 200 OK for liveness checks while distributed cluster starts (#8176) 2019-09-05 14:50:56 +05:30
docker-swarm Return 200 OK for liveness checks while distributed cluster starts (#8176) 2019-09-05 14:50:56 +05:30
kubernetes Update orchestration docs to use ellipses syntax (#8153) 2019-09-01 10:02:15 -07:00
README.md Removes the incorrect coverage badge from the docs (#7651) 2019-05-16 12:11:49 +05:30

README.md

MinIO Deployment Quickstart Guide Slack Go Report Card Docker Pulls

MinIO is a cloud-native application designed to scale in a sustainable manner in multi-tenant environments. Orchestration platforms provide perfect launchpad for MinIO to scale. Below is the list of MinIO deployment documents for various orchestration platforms:

Orchestration platforms
Docker Swarm
Docker Compose
Kubernetes
DC/OS

Why is MinIO cloud-native?

The term cloud-native revolves around the idea of applications deployed as micro services, that scale well. It is not about just retrofitting monolithic applications onto modern container based compute environment. A cloud-native application is portable and resilient by design, and can scale horizontally by simply replicating. Modern orchestration platforms like Swarm, Kubernetes and DC/OS make replicating and managing containers in huge clusters easier than ever.

While containers provide isolated application execution environment, orchestration platforms allow seamless scaling by helping replicate and manage containers. MinIO extends this by adding isolated storage environment for each tenant.

MinIO is built ground up on the cloud-native premise. With features like erasure-coding, distributed and shared setup, it focuses only on storage and does it very well. While, it can be scaled by just replicating MinIO instances per tenant via an orchestration platform.

In a cloud-native environment, scalability is not a function of the application but the orchestration platform.

In a typical modern infrastructure deployment, application, database, key-store, etc. already live in containers and are managed by orchestration platforms. MinIO brings robust, scalable, AWS S3 compatible object storage to the lot.

Cloud-native