Closed dlohin closed 6 years ago
I'll do an installation test tonight.
@dlohin What can I use to validate that it's working correctly (something that provisions a PV and creates a claim)
Create the following claim:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: edsnfs
annotations:
volume.beta.kubernetes.io/storage-class: "edcop-nfs"
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Mi
After a bit you should be able to see the status of the PVC switch to bound:
[root@minion-5318 ~]# kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE edsnfs Bound pvc-7f2af7e7-42ff-11e8-94cc-28ac9e7ca5e3 1Mi RWX edcop-nfs 4s
A PV should have been created that corresponds to the pvc: [root@minion-5318 ~]# kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-7f2af7e7-42ff-11e8-94cc-28ac9e7ca5e3 1Mi RWX Delete Bound default/edsnfs edcop-nfs 35s
…de labelled edcop.io/nfs-storage=true will have NFS deployed.