...
Let's try to summarize the steps carried out thanks to the visual aid of the screen below. The operations carried out, in chronological order, are (use the AGE column as a reference):
- creation of a large default storage, through
sc/local-storageandpv/local-pv; - deployment of the NFS Server (
nfs.yaml), which generates thepvc/nfs-default-claimlinked to thepv/local-pv; - administrator creates
sc/rook-nfs-share1with provisionerrook-nfs-provisioner; - the user creates
pvc/rook-nfs-pv-claim, which dynamically generates a small volume, within its namespace; - the user can create other volumes in the same or other namespaces.
| Code Block | ||||
|---|---|---|---|---|
| ||||
# With this command you get SC, PV and PVC (of all namespaces) $ kubectl get sc,pv,pvc -A NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE sc/local-storage (default) kubernetes.io/no-provisioner Delete WaitForFirstConsumer false 60m sc/rook-nfs-share1 nfs.rook.io/rook-nfs-provisioner Delete Immediate false 40m50m NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS AGE pv/local-pv 10Gi RWX Delete Bound rook-nfs/nfs-default-claim local-storage 50m58m pv/pvc-66761edb-0b68-4a6e-92c2-016c9ecf1255 10Mi RWX Delete Bound myns/rook-nfs-pv-claim rook-nfs-share 40m pv/pvc-9cc3bb63-eb0b-4ded-bbb9-3d854e7c6b4b 15Mi RWX Retain Bound myns/rook-nfs-pv-claim2 rook-nfs-share1 30m NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE rook-nfs pvc/nfs-default-claim Bound local-pv 10Gi RWX local-storage 45m56m myns pvc/rook-nfs-pv-claim Bound pvc-66761edb-0b68-4a6e-92c2-016c9ecf1255 10Mi RWX rook-nfs-share1 40m myns pvc/rook-nfs-pv-claim2 Bound pvc-9cc3bb63-eb0b-4ded-bbb9-3d854e7c6b4b 15Mi RWX rook-nfs-share1 30m |