fix PVC path in storage doc
Found a small error with the PVC path and ended up fixing a few nits.
@@ -14,7 +14,7 @@ The hostPath provisioner needs to write to a directory on the node, we will need
cluster/cli.sh ssh node01 -- sudo mkdir /var/run/kubevirt/hostpath
```
-## deploy hostPath PVC provisioner
+## Deploy hostPath PVC provisioner
We are using the hostPath provisioner from [here](https://github.com/MaZderMind/hostpath-provisioner). Simply run from :
@@ -29,9 +29,9 @@ This will create
- hostpath-provisioner Deployment
- Create hostpath Storage Class, set as the default, so any Persistent Volume Claims (PVCs) will be serviced by this storage class
-After a few moments the hostpath-provisioner pod should be running, we are now ready to create PVCs against it. Any requested PVCs will be stored in /var/run/kubevirt/<pvc-name>-<hash>. The PV retention policy will be delete, which means that when you delete the PVC, the matching PV is also removed and the directory created on the host is removed as well.
+After a few moments the hostpath-provisioner pod should be running, we are now ready to create PVCs against it. Any requested PVCs will be stored in `/var/run/kubevirt/hostpath/<pvc-name>-<hash>`. The PV retention policy will be `delete`, which means that when you delete the PVC, the matching PV is also removed and the directory created on the host is removed as well.
-## deploy CDI controller
+## Deploy CDI controller
The Containerized Data Importer controller is a controller that watches for PVCs with a specific annotation. If that annotation is detected, it will use the 'storage.image.endpoint' URL to download the image, convert it if needed and write it to the requested PVC. One can then use the PVC to start a VM using the image in it. To deploy the CDI controller run this:
@@ -68,9 +68,9 @@ spec:
storage: 20Mi
```
-As you can see we are creating a PVC named 'image-pvc' with 2 annotations. In this case we are requesting the cirros image because its a small image, but any http or s3 end point will do. If you need to provide a secret the second annotation can be used to provide it. In our example we don't need a secret.
+As you can see we are creating a PVC named 'image-pvc' with 2 annotations. In this case we are requesting the cirros image because it's a small image, but any http or s3 end point will do. If you need to provide a secret the second annotation can be used to provide it. In our example we don't need a secret.
-We CDI controller will see the annotation and spawn an 'importer' pod that does the actual work. Once the pod is finished there will be a disk.img in the PVC.
+The CDI controller will see the annotation and spawn an 'importer' pod that does the actual work. Once the pod is finished there will be a disk.img in the PVC.
## Create a VM using the image
