2015-07-13 20:13:09 -04:00
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- BEGIN STRIP_FOR_RELEASE -->
2015-07-16 13:02:26 -04:00
< img src = "http://kubernetes.io/img/warning.png" alt = "WARNING"
width="25" height="25">
< img src = "http://kubernetes.io/img/warning.png" alt = "WARNING"
width="25" height="25">
< img src = "http://kubernetes.io/img/warning.png" alt = "WARNING"
width="25" height="25">
< img src = "http://kubernetes.io/img/warning.png" alt = "WARNING"
width="25" height="25">
< img src = "http://kubernetes.io/img/warning.png" alt = "WARNING"
width="25" height="25">
< h2 > PLEASE NOTE: This document applies to the HEAD of the source tree< / h2 >
If you are using a released version of Kubernetes, you should
refer to the docs that go with that version.
2015-12-14 13:37:38 -05:00
<!-- TAG RELEASE_LINK, added by the munger automatically -->
2015-07-16 13:02:26 -04:00
< strong >
2015-11-03 13:17:57 -05:00
The latest release of this document can be found
[here ](http://releases.k8s.io/release-1.1/examples/glusterfs/README.md ).
2015-07-16 13:02:26 -04:00
Documentation for other releases can be found at
[releases.k8s.io ](http://releases.k8s.io ).
< / strong >
--
2015-07-13 18:15:35 -04:00
2015-07-13 20:13:09 -04:00
<!-- END STRIP_FOR_RELEASE -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
2015-07-17 18:35:41 -04:00
2015-03-26 14:53:21 -04:00
## Glusterfs
[Glusterfs ](http://www.gluster.org ) is an open source scale-out filesystem. These examples provide information about how to allow containers use Glusterfs volumes.
2015-05-14 14:59:34 -04:00
The example assumes that you have already set up a Glusterfs server cluster and the Glusterfs client package is installed on all Kubernetes nodes.
2015-03-26 14:53:21 -04:00
### Prerequisites
2015-05-14 14:59:34 -04:00
Set up Glusterfs server cluster; install Glusterfs client package on the Kubernetes nodes. ([Guide](https://www.howtoforge.com/high-availability-storage-with-glusterfs-3.2.x-on-debian-wheezy-automatic-file-replication-mirror-across-two-storage-servers))
### Create endpoints
2015-07-17 18:35:41 -04:00
2015-05-24 03:15:58 -04:00
Here is a snippet of [glusterfs-endpoints.json ](glusterfs-endpoints.json ),
2015-05-14 14:59:34 -04:00
```
"addresses": [
{
"IP": "10.240.106.152"
}
],
"ports": [
{
2015-06-09 19:06:14 -04:00
"port": 1
2015-05-14 14:59:34 -04:00
}
]
```
2015-07-16 22:01:02 -04:00
2015-07-24 17:52:18 -04:00
The "IP" field should be filled with the address of a node in the Glusterfs server cluster. In this example, it is fine to give any valid value (from 1 to 65535) to the "port" field.
2015-05-14 14:59:34 -04:00
Create the endpoints,
2015-07-16 22:01:02 -04:00
2015-07-20 12:40:32 -04:00
```sh
2015-05-14 14:59:34 -04:00
$ kubectl create -f examples/glusterfs/glusterfs-endpoints.json
```
You can verify that the endpoints are successfully created by running
2015-07-16 22:01:02 -04:00
2015-07-20 12:40:32 -04:00
```sh
2015-07-07 14:20:33 -04:00
$ kubectl get endpoints
2015-05-14 14:59:34 -04:00
NAME ENDPOINTS
glusterfs-cluster 10.240.106.152:1,10.240.79.157:1
```
2015-03-26 14:53:21 -04:00
2015-08-31 01:52:51 -04:00
We need also create a service for this endpoints, so that the endpoints will be persistented. We will add this service without a selector to tell Kubernetes we want to add its endpoints manually. You can see [glusterfs-service.json ](glusterfs-service.json ) for details.
Use this command to create the service:
```sh
$ kubectl create -f examples/glusterfs/glusterfs-service.json
```
2015-03-26 14:53:21 -04:00
### Create a POD
2015-05-24 03:15:58 -04:00
The following *volume* spec in [glusterfs-pod.json ](glusterfs-pod.json ) illustrates a sample configuration.
2015-03-26 14:53:21 -04:00
2015-07-20 12:40:32 -04:00
```json
2015-03-26 14:53:21 -04:00
{
"name": "glusterfsvol",
"glusterfs": {
"endpoints": "glusterfs-cluster",
"path": "kube_vol",
"readOnly": true
}
}
```
2015-07-24 17:52:18 -04:00
The parameters are explained as the followings.
2015-03-26 14:53:21 -04:00
2015-07-24 17:52:18 -04:00
- **endpoints** is endpoints name that represents a Gluster cluster configuration. *kubelet* is optimized to avoid mount storm, it will randomly pick one from the endpoints to mount. If this host is unresponsive, the next Gluster host in the endpoints is automatically selected.
- **path** is the Glusterfs volume name.
- **readOnly** is the boolean that sets the mountpoint readOnly or readWrite.
2015-03-26 14:53:21 -04:00
2015-05-14 14:59:34 -04:00
Create a pod that has a container using Glusterfs volume,
2015-07-16 22:01:02 -04:00
2015-07-20 12:40:32 -04:00
```sh
2015-05-14 14:59:34 -04:00
$ kubectl create -f examples/glusterfs/glusterfs-pod.json
2015-03-26 14:53:21 -04:00
```
2015-07-16 22:01:02 -04:00
2015-05-14 14:59:34 -04:00
You can verify that the pod is running:
2015-03-26 14:53:21 -04:00
2015-07-20 12:40:32 -04:00
```sh
2015-03-26 14:53:21 -04:00
$ kubectl get pods
2015-07-07 14:20:33 -04:00
NAME READY STATUS RESTARTS AGE
glusterfs 1/1 Running 0 3m
2015-05-14 14:59:34 -04:00
2015-07-07 14:20:33 -04:00
$ kubectl get pods glusterfs -t '{{.status.hostIP}}{{"\n"}}'
10.240.169.172
2015-05-14 14:59:34 -04:00
```
2015-07-07 14:20:33 -04:00
You may ssh to the host (the hostIP) and run 'mount' to see if the Glusterfs volume is mounted,
2015-07-16 22:01:02 -04:00
2015-07-20 12:40:32 -04:00
```sh
2015-05-14 14:59:34 -04:00
$ mount | grep kube_vol
10.240.106.152:kube_vol on /var/lib/kubelet/pods/f164a571-fa68-11e4-ad5c-42010af019b7/volumes/kubernetes.io~glusterfs/glusterfsvol type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
2015-03-26 14:53:21 -04:00
```
2015-05-14 14:59:34 -04:00
You may also run `docker ps` on the host to see the actual container.
2015-05-14 18:12:45 -04:00
2015-07-13 20:13:09 -04:00
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
2015-05-14 18:12:45 -04:00
[]()
2015-07-13 20:13:09 -04:00
<!-- END MUNGE: GENERATED_ANALYTICS -->