Updated read

This commit is contained in:
Nitish 2017-02-13 23:19:29 +05:30
parent 6d121b49b5
commit dd20e14ceb

View File

@ -1,18 +1,20 @@
# Cloud Native Deployment of Minio using Kubernetes
# Cloud Native Deployment of Minio using Kubernetes
## Table of Contents
## Table of Contents
- [Introduction](#introduction)
- [Prerequisites](#prerequisites)
- [Minio Docker](#minio-docker)
- [Get Started](#get-started)
## Introduction
Minio is an AWS S3 compatible, object storage server built for cloud applications and devops.
The following document describes the process to deploy [Minio](https://minio.io/) on Kubernetes. Minio is a _cloud native_ application, meaning
Minio understands that it is running within a cluster manager, and uses this cluster management infrastructure for allocation of compute and storage
resources.
This example uses some of the core components of Kubernetes:
The pods use the [official Minio Docker image](https://hub.docker.com/r/minio/minio/~/dockerfile/) from Docker Hub. This example uses some of the core components of Kubernetes:
- [_Pods_](https://kubernetes.io/docs/user-guide/pods/)
- [_Services_](https://kubernetes.io/docs/user-guide/services/)
@ -27,10 +29,6 @@
[getting started guides](../../../docs/getting-started-guides/)
for installation instructions for your platform.
## Minio Docker
The pods use the [official Minio Docker image](https://hub.docker.com/r/minio/minio/~/dockerfile/) from Docker Hub.
## Get Started
But before creating the deployment, you need to create a persistent volume claim (PVC) to request storage for the Minio instance. Kubernetes looks out for PVs matching the PVC request in the cluster and binds it to the PVC automatically. Create a PersistentVolumeClaim by downloading the file [minio-standalone-pvc.yaml] (minio-standalone-pvc.yaml?raw=true) and running