text stringlengths 0 59.1k |
|---|
``` |
Then using the created PVC, create an NFS server and service: |
```console |
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-deployment.yaml |
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-service.yaml |
``` |
The directory contains dummy `index.html`. Wait until the pod is running |
by checking `kubectl get pods -l role=nfs-server`. |
### Create the NFS based persistent volume claim |
The [NFS busybox deployment](nfs-busybox-deployment.yaml) uses a simple script to |
generate data written to the NFS server we just started. First, you'll need to |
find the cluster IP of the server: |
```console |
$ kubectl describe services nfs-server |
``` |
Replace the invalid IP in the [nfs PV](nfs-pv.yaml). (In the future, |
we'll be able to tie these together using the service names, but for |
now, you have to hardcode the IP.) |
Create the [persistent volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) |
and the persistent volume claim for your NFS server. The persistent volume and |
claim gives us an indirection that allow multiple pods to refer to the NFS |
server using a symbolic name rather than the hardcoded server address. |
```console |
$ kubectl create -f examples/staging/volumes/nfs/nfs-pv.yaml |
$ kubectl create -f examples/staging/volumes/nfs/nfs-pvc.yaml |
``` |
## Setup the fake backend |
The [NFS busybox deployment](nfs-busybox-deployment.yaml) updates `index.html` on the |
NFS server every 10 seconds. Let's start that now: |
```console |
$ kubectl create -f examples/staging/volumes/nfs/nfs-busybox-deployment.yaml |
``` |
Conveniently, it's also a `busybox` pod, so we can get an early check |
that our mounts are working now. Find a busybox pod and exec: |
```console |
$ kubectl get pod -l name=nfs-busybox |
NAME READY STATUS RESTARTS AGE |
nfs-busybox-jdhf3 1/1 Running 0 25m |
nfs-busybox-w3s4t 1/1 Running 0 25m |
$ kubectl exec nfs-busybox-jdhf3 -- cat /mnt/index.html |
Thu Oct 22 19:20:18 UTC 2015 |
nfs-busybox-w3s4t |
``` |
You should see output similar to the above if everything is working well. If |
it's not, make sure you changed the invalid IP in the [NFS PV](nfs-pv.yaml) file |
and make sure the `describe services` command above had endpoints listed |
(indicating the service was associated with a running pod). |
### Setup the web server |
The [web server deployment](nfs-web-deployment.yaml) is an another simple |
deployment demonstrates reading from the NFS share exported above as a NFS |
volume and runs a simple web server on it. |
Define the pod: |
```console |
$ kubectl create -f examples/staging/volumes/nfs/nfs-web-deployment.yaml |
``` |
This creates two pods, each of which serve the `index.html` from above. We can |
then use a simple service to front it: |
```console |
$ kubectl create -f examples/staging/volumes/nfs/nfs-web-service.yaml |
``` |
We can then use the busybox container we launched before to check that `nginx` |
is serving the data appropriately: |
```console |
$ kubectl get pod -l name=nfs-busybox |
NAME READY STATUS RESTARTS AGE |
nfs-busybox-jdhf3 1/1 Running 0 1h |
nfs-busybox-w3s4t 1/1 Running 0 1h |
$ kubectl get services nfs-web |
NAME LABELS SELECTOR IP(S) PORT(S) |
nfs-web <none> role=web-frontend 10.0.68.37 80/TCP |
$ kubectl exec nfs-busybox-jdhf3 -- wget -qO- http://10.0.68.37 |
Thu Oct 22 19:28:55 UTC 2015 |
nfs-busybox-w3s4t |
``` |
<|endoftext|> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.