1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/persistent-storage-hostpath-static-provisioning.adoc

68 lines
1.7 KiB
Plaintext

// Module included in the following assemblies:
//
// * storage/persistent_storage/persistent-storage-hostpath.adoc
:_mod-docs-content-type: PROCEDURE
[id="hostpath-static-provisioning_{context}"]
= Statically provisioning hostPath volumes
A pod that uses a hostPath volume must be referenced by manual (static) provisioning.
.Procedure
. Define the persistent volume (PV) by creating a `pv.yaml` file with the `PersistentVolume` object definition:
+
[source,yaml]
----
apiVersion: v1
kind: PersistentVolume
metadata:
name: task-pv-volume <1>
labels:
type: local
spec:
storageClassName: manual <2>
capacity:
storage: 5Gi
accessModes:
- ReadWriteOnce <3>
persistentVolumeReclaimPolicy: Retain
hostPath:
path: "/mnt/data" <4>
----
<1> The name of the volume. This name is how the volume is identified by persistent volume (PV) claims or pods.
<2> Used to bind persistent volume claim (PVC) requests to the PV.
<3> The volume can be mounted as `read-write` by a single node.
<4> The configuration file specifies that the volume is at `/mnt/data` on the cluster's node. To avoid corrupting your host system, do not mount to the container root, `/`, or any path that is the same in the host and the container. You can safely mount the host by using `/host`
. Create the PV from the file:
+
[source,terminal]
----
$ oc create -f pv.yaml
----
. Define the PVC by creating a `pvc.yaml` file with the `PersistentVolumeClaim` object definition:
+
[source,yaml]
----
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: task-pvc-volume
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: manual
----
. Create the PVC from the file:
+
[source,terminal]
----
$ oc create -f pvc.yaml
----