text stringlengths 0 59.1k |
|---|
- name: storage # must match the volume name, above |
mountPath: "/storage" |
``` |
Create the Deployment |
```sh |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-deployment.yaml |
deployment "minio-deployment" created |
``` |
### Step 3: Create Minio Service |
Now that you have a Minio deployment running, you may either want to access it internally (within the cluster) or expose it as a Service onto an external (outside of your cluster, maybe public internet) IP address, depending on your use case. You can achieve this using Services. There are 3 major service types — defaul... |
In this example, we expose the Minio Deployment by creating a LoadBalancer service. This is the service description. |
```sh |
apiVersion: v1 |
kind: Service |
metadata: |
name: minio-service |
spec: |
type: LoadBalancer |
ports: |
- port: 9000 |
targetPort: 9000 |
protocol: TCP |
selector: |
app: minio |
``` |
Create the Minio service |
```sh |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-standalone-service.yaml |
service "minio-service" created |
``` |
The `LoadBalancer` service takes couple of minutes to launch. To check if the service was created successfully, run the command |
```sh |
kubectl get svc minio-service |
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE |
minio-service 10.55.248.23 104.199.249.165 9000:31852/TCP 1m |
``` |
### Step 4: Resource cleanup |
Once you are done, cleanup the cluster using |
```sh |
kubectl delete deployment minio-deployment \ |
&& kubectl delete pvc minio-pv-claim \ |
&& kubectl delete svc minio-service |
``` |
## Minio Distributed Server Deployment |
The following document describes the process to deploy [distributed Minio](https://docs.minio.io/docs/distributed-minio-quickstart-guide) server on Kubernetes. This example uses the [official Minio Docker image](https://hub.docker.com/r/minio/minio/~/dockerfile/) from Docker Hub. |
This example uses following core components of Kubernetes: |
- [_Pods_](https://kubernetes.io/docs/concepts/workloads/pods/pod/) |
- [_Services_](https://kubernetes.io/docs/concepts/services-networking/service/) |
- [_Statefulsets_](https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/) |
### Distributed Quickstart |
Run the below commands to get started quickly |
```sh |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-distributed-headless-service.yaml |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-distributed-statefulset.yaml |
kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/staging/storage/minio/minio-distributed-service.yaml |
``` |
### Step 1: Create Minio Headless Service |
Headless Service controls the domain within which StatefulSets are created. The domain managed by this Service takes the form: `$(service name).$(namespace).svc.cluster.local` (where “cluster.local” is the cluster domain), and the pods in this domain take the form: `$(pod-name-{i}).$(service name).$(namespace).svc.clus... |
This is the Headless service description. |
```sh |
apiVersion: v1 |
kind: Service |
metadata: |
name: minio |
labels: |
app: minio |
spec: |
clusterIP: None |
ports: |
- port: 9000 |
name: minio |
selector: |
app: minio |
``` |
Create the Headless Service |
```sh |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.