@@ -29,15 +29,15 @@ $ kubectl create -f examples/staging/volumes/nfs/provisioner/nfs-server-gce-pv.y
29
29
# On Azure (create Azure Disk PVC):
30
30
$ kubectl create -f examples/staging/volumes/nfs/provisioner/nfs-server-azure-pv.yaml
31
31
# Common steps after creating either GCE PD or Azure Disk PVC:
32
- $ kubectl create -f examples/staging/volumes/nfs/nfs-server-rc .yaml
32
+ $ kubectl create -f examples/staging/volumes/nfs/nfs-server-deployment .yaml
33
33
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-service.yaml
34
34
# get the cluster IP of the server using the following command
35
35
$ kubectl describe services nfs-server
36
36
# use the NFS server IP to update nfs-pv.yaml and execute the following
37
37
$ kubectl create -f examples/staging/volumes/nfs/nfs-pv.yaml
38
38
$ kubectl create -f examples/staging/volumes/nfs/nfs-pvc.yaml
39
39
# run a fake backend
40
- $ kubectl create -f examples/staging/volumes/nfs/nfs-busybox-rc .yaml
40
+ $ kubectl create -f examples/staging/volumes/nfs/nfs-busybox-deployment .yaml
41
41
# get pod name from this command
42
42
$ kubectl get pod -l name=nfs-busybox
43
43
# use the pod name to check the test file
@@ -46,19 +46,19 @@ $ kubectl exec nfs-busybox-jdhf3 -- cat /mnt/index.html
46
46
47
47
## Example of NFS based persistent volume
48
48
49
- See [ NFS Service and Replication Controller ] ( nfs-web-rc .yaml ) for a quick example of how to use an NFS
50
- volume claim in a replication controller . It relies on the
49
+ See [ NFS Service and Deployment ] ( nfs-web-deployment .yaml ) for a quick example of how to use an NFS
50
+ volume claim in a deployment . It relies on the
51
51
[ NFS persistent volume] ( nfs-pv.yaml ) and
52
52
[ NFS persistent volume claim] ( nfs-pvc.yaml ) in this example as well.
53
53
54
54
## Complete setup
55
55
56
- The example below shows how to export a NFS share from a single pod replication
57
- controller and import it into two replication controllers .
56
+ The example below shows how to export a NFS share from a single pod
57
+ deployment and import it into two deployments .
58
58
59
59
### NFS server part
60
60
61
- Define [ the NFS Service and Replication Controller ] ( nfs-server-rc .yaml ) and
61
+ Define [ the NFS Service and Deployment ] ( nfs-server-deployment .yaml ) and
62
62
[ NFS service] ( nfs-server-service.yaml ) :
63
63
64
64
The NFS server exports an auto-provisioned persistent volume backed by GCE PD or Azure Disk. If you are on GCE, create a GCE PD-based PVC:
@@ -76,7 +76,7 @@ $ kubectl create -f examples/staging/volumes/nfs/provisioner/nfs-server-azure-pv
76
76
Then using the created PVC, create an NFS server and service:
77
77
78
78
``` console
79
- $ kubectl create -f examples/staging/volumes/nfs/nfs-server-rc .yaml
79
+ $ kubectl create -f examples/staging/volumes/nfs/nfs-server-deployment .yaml
80
80
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-service.yaml
81
81
```
82
82
@@ -85,7 +85,7 @@ by checking `kubectl get pods -l role=nfs-server`.
85
85
86
86
### Create the NFS based persistent volume claim
87
87
88
- The [ NFS busybox controller ] ( nfs-busybox-rc .yaml ) uses a simple script to
88
+ The [ NFS busybox deployment ] ( nfs-busybox-deployment .yaml ) uses a simple script to
89
89
generate data written to the NFS server we just started. First, you'll need to
90
90
find the cluster IP of the server:
91
91
@@ -110,11 +110,11 @@ $ kubectl create -f examples/staging/volumes/nfs/nfs-pvc.yaml
110
110
111
111
## Setup the fake backend
112
112
113
- The [ NFS busybox controller ] ( nfs-busybox-rc .yaml ) updates ` index.html ` on the
113
+ The [ NFS busybox deployment ] ( nfs-busybox-deployment .yaml ) updates ` index.html ` on the
114
114
NFS server every 10 seconds. Let's start that now:
115
115
116
116
``` console
117
- $ kubectl create -f examples/staging/volumes/nfs/nfs-busybox-rc .yaml
117
+ $ kubectl create -f examples/staging/volumes/nfs/nfs-busybox-deployment .yaml
118
118
```
119
119
120
120
Conveniently, it's also a ` busybox ` pod, so we can get an early check
@@ -137,14 +137,14 @@ and make sure the `describe services` command above had endpoints listed
137
137
138
138
### Setup the web server
139
139
140
- The [ web server controller ] ( nfs-web-rc .yaml ) is an another simple replication
141
- controller demonstrates reading from the NFS share exported above as a NFS
140
+ The [ web server deployment ] ( nfs-web-deployment .yaml ) is an another simple
141
+ deployment demonstrates reading from the NFS share exported above as a NFS
142
142
volume and runs a simple web server on it.
143
143
144
144
Define the pod:
145
145
146
146
``` console
147
- $ kubectl create -f examples/staging/volumes/nfs/nfs-web-rc .yaml
147
+ $ kubectl create -f examples/staging/volumes/nfs/nfs-web-deployment .yaml
148
148
```
149
149
150
150
This creates two pods, each of which serve the ` index.html ` from above. We can
0 commit comments