Kubernetes Persistent Volume Claim Manifest: Difference between revisions
Jump to navigation
Jump to search
Line 28: | Line 28: | ||
Name of the [[Kubernetes_Storage_Concepts#Storage_Class_.28SC.29|StorageClass]] required by the claim. For a description of the claim behavior when no storage class name is present, see [[Kubernetes_Storage_Concepts#Persistent_Volume_Claims_and_Storage_Class|Persistent Volume Claims and Storage Class]]. | Name of the [[Kubernetes_Storage_Concepts#Storage_Class_.28SC.29|StorageClass]] required by the claim. For a description of the claim behavior when no storage class name is present, see [[Kubernetes_Storage_Concepts#Persistent_Volume_Claims_and_Storage_Class|Persistent Volume Claims and Storage Class]]. | ||
==volumeName== | |||
<font color=darkgray>TODO</font> | |||
==volumeMode== | ==volumeMode== |
Revision as of 17:49, 28 August 2020
External
Internal
Example
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc1 spec: accessModes: - RedWriteOnce storageClassName: test # volumeName: testVolume resources: requests: storage: 10 Gi ...
.spec Elements
The values in the .spec section must match with the persistent volume it intends to bind with. Persistent volume's access mode, storage class name and capacity must match.
accessModes
storageClassName
Name of the StorageClass required by the claim. For a description of the claim behavior when no storage class name is present, see Persistent Volume Claims and Storage Class.
volumeName
TODO
volumeMode
'volumeMode' defines what type of volume is required by the claim. Value of "Filesystem" is implied when not included in claim spec