Skip to content

Commit 5b19874

Browse files
committed
Updating README to reflect changes from #442
1 parent 8c357b6 commit 5b19874

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

staging/volumes/nfs/README.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,15 @@ $ kubectl create -f examples/staging/volumes/nfs/provisioner/nfs-server-gce-pv.y
2929
# On Azure (create Azure Disk PVC):
3030
$ kubectl create -f examples/staging/volumes/nfs/provisioner/nfs-server-azure-pv.yaml
3131
# 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
3333
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-service.yaml
3434
# get the cluster IP of the server using the following command
3535
$ kubectl describe services nfs-server
3636
# use the NFS server IP to update nfs-pv.yaml and execute the following
3737
$ kubectl create -f examples/staging/volumes/nfs/nfs-pv.yaml
3838
$ kubectl create -f examples/staging/volumes/nfs/nfs-pvc.yaml
3939
# 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
4141
# get pod name from this command
4242
$ kubectl get pod -l name=nfs-busybox
4343
# use the pod name to check the test file
@@ -46,19 +46,19 @@ $ kubectl exec nfs-busybox-jdhf3 -- cat /mnt/index.html
4646

4747
## Example of NFS based persistent volume
4848

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
5151
[NFS persistent volume](nfs-pv.yaml) and
5252
[NFS persistent volume claim](nfs-pvc.yaml) in this example as well.
5353

5454
## Complete setup
5555

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.
5858

5959
### NFS server part
6060

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
6262
[NFS service](nfs-server-service.yaml):
6363

6464
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
7676
Then using the created PVC, create an NFS server and service:
7777

7878
```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
8080
$ kubectl create -f examples/staging/volumes/nfs/nfs-server-service.yaml
8181
```
8282

@@ -85,7 +85,7 @@ by checking `kubectl get pods -l role=nfs-server`.
8585

8686
### Create the NFS based persistent volume claim
8787

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
8989
generate data written to the NFS server we just started. First, you'll need to
9090
find the cluster IP of the server:
9191

@@ -110,11 +110,11 @@ $ kubectl create -f examples/staging/volumes/nfs/nfs-pvc.yaml
110110

111111
## Setup the fake backend
112112

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
114114
NFS server every 10 seconds. Let's start that now:
115115

116116
```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
118118
```
119119

120120
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
137137

138138
### Setup the web server
139139

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
142142
volume and runs a simple web server on it.
143143

144144
Define the pod:
145145

146146
```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
148148
```
149149

150150
This creates two pods, each of which serve the `index.html` from above. We can

0 commit comments

Comments
 (0)