website/content/en/examples/pods/storage/pv-volume.yaml

apiVersion: v1
kind: PersistentVolume
metadata:
  name: task-pv-volume
  labels:
    type: local
spec:
  storageClassName: manual
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/mnt/data"
Write new Task: Configuring a Pod to use a PersistentVolume. 2017-01-17 20:04:57 +00:00			`apiVersion: v1`
Fix orders of yaml for examples. (#15763) 2019-08-09 21:33:15 +00:00			`kind: PersistentVolume`
Write new Task: Configuring a Pod to use a PersistentVolume. 2017-01-17 20:04:57 +00:00			`metadata:`
			`name: task-pv-volume`
			`labels:`
			`type: local`
			`spec:`
update pod persistent volume example storage class (#3979) * update pod persistent volume example storage class When binding to a manually created PersistentVolume, the claim must disable dynamic provisioning by specifying an empty storage class. Fixes #2803 * use specific storageclass * revert gibibytes -> gigabytes change 2017-06-14 06:55:58 +00:00			`storageClassName: manual`
Write new Task: Configuring a Pod to use a PersistentVolume. 2017-01-17 20:04:57 +00:00			`capacity:`
			`storage: 10Gi`
			`accessModes:`
			`- ReadWriteOnce`
			`hostPath:`
change path to reflect guide The "Configure a Pod to Use a PersistentVolume for Storage"-task specifies that the content should be located on "/mnt/data" and not "/tmp/data", however this is not reflected in the yaml. 2018-01-19 08:30:32 +00:00			`path: "/mnt/data"`