OpenShift PersistentVolume Operations: Difference between revisions
Jump to navigation
Jump to search
Line 55: | Line 55: | ||
Note that the volume, even if available, it won't be used until a matching [[OpenShift_Concepts#Persistent_Volume_Claim|persistent volume claim]] is declared. | Note that the volume, even if available, it won't be used until a matching [[OpenShift_Concepts#Persistent_Volume_Claim|persistent volume claim]] is declared. | ||
=Create a Persistent Volume Claim= | |||
=Associate a Persistent Volume Claim with a Deployment Configuration= |
Revision as of 23:46, 1 November 2017
External
Internal
Delete a Persistent Volume
oc delete pv <persistent-volume-name>
oc delete pv metrics-volume
Create a Persistent Volume
NFS
Provision the Underlying Storage
Create the Persistent Volume Definition File
Create a "pv.yaml" file with the following content:
apiVersion: v1 kind: PersistentVolume metadata: name: metrics-volume spec: capacity: storage: 10Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain nfs: path: /support-nfs-storage/metrics server: support.local
Make sure the "support.local" server is accessible from any node that will use the volume, and the /support-nfs-storage/metrics is exported and has sufficient permissions.
Create the Volume
oc create -f pv.yaml
Once created, it will shows as:
oc get pv NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM REASON AGE ... metrics-volume 10Gi RWO Retain Available 25s ...
Note that the volume, even if available, it won't be used until a matching persistent volume claim is declared.