text stringlengths 0 59.1k |
|---|
This section uses following core components of Kubernetes: |
- [_Pods_](https://kubernetes.io/docs/user-guide/pods/) |
- [_Services_](https://kubernetes.io/docs/user-guide/services/) |
- [_Deployments_](https://kubernetes.io/docs/user-guide/deployments/) |
- [_Persistent Volume Claims_](https://kubernetes.io/docs/user-guide/persistent-volumes/#persistentvolumeclaims) |
### Standalone Quickstart |
Run the below commands to get started quickly |
```sh |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-pvc.yaml |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-deployment.yaml |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-service.yaml |
``` |
### Step 1: Create Persistent Volume Claim |
Minio needs persistent storage to store objects. If there is no |
persistent storage, the data stored in Minio instance will be stored in the container file system and will be wiped off as soon as the container restarts. |
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. |
This is the PVC description. |
```sh |
apiVersion: v1 |
kind: PersistentVolumeClaim |
metadata: |
# This name uniquely identifies the PVC. Will be used in deployment below. |
name: minio-pv-claim |
labels: |
app: minio-storage-claim |
spec: |
# Read more about access modes here: http://kubernetes.io/docs/user-guide/persistent-volumes/#access-modes |
accessModes: |
- ReadWriteOnce |
storageClassName: standard |
resources: |
# This is the request for storage. Should be available in the cluster. |
requests: |
storage: 10Gi |
``` |
Create the PersistentVolumeClaim |
```sh |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-pvc.yaml |
persistentvolumeclaim "minio-pv-claim" created |
``` |
### Step 2: Create Minio Deployment |
A deployment encapsulates replica sets and pods — so, if a pod goes down, replication controller makes sure another pod comes up automatically. This way you won’t need to bother about pod failures and will have a stable Minio service available. |
This is the deployment description. |
```sh |
apiVersion: apps/v1 # for k8s versions before 1.9.0 use apps/v1beta2 and before 1.8.0 use extensions/v1beta1 |
kind: Deployment |
metadata: |
# This name uniquely identifies the Deployment |
name: minio-deployment |
spec: |
selector: |
matchLabels: |
app: minio |
strategy: |
type: Recreate |
template: |
metadata: |
labels: |
# Label is used as selector in the service. |
app: minio |
spec: |
# Refer to the PVC created earlier |
volumes: |
- name: storage |
persistentVolumeClaim: |
# Name of the PVC created earlier |
claimName: minio-pv-claim |
containers: |
- name: minio |
# Pulls the default Minio image from Docker Hub |
image: minio/minio:latest |
args: |
- server |
- /storage |
env: |
# Minio access key and secret key |
- name: MINIO_ACCESS_KEY |
value: "minio" |
- name: MINIO_SECRET_KEY |
value: "minio123" |
ports: |
- containerPort: 9000 |
hostPort: 9000 |
# Mount the volume into the pod |
volumeMounts: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.