Skip to content

[enterprise-4.13] OCPBUGS#12622: Fixed Statically provisioning hostPath volumes bug #84807

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 12, 2024
Merged

[enterprise-4.13] OCPBUGS#12622: Fixed Statically provisioning hostPath volumes bug #84807

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 20 additions & 20 deletions modules/persistent-storage-hostpath-static-provisioning.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,30 +10,30 @@ A pod that uses a hostPath volume must be referenced by manual (static) provisio

.Procedure

. Define the persistent volume (PV). Create a file, `pv.yaml`, with the `PersistentVolume` object definition:
. 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>
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 it is identified by persistent volume claims or pods.
<2> Used to bind persistent volume claim requests to this persistent volume.
<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. Do not mount to the container root, `/`, or any path that is the same in the host and the container. This can corrupt your host system. It is safe to mount the host by using `/host`.
<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:
+
Expand All @@ -42,7 +42,7 @@ A pod that uses a hostPath volume must be referenced by manual (static) provisio
$ oc create -f pv.yaml
----

. Define the persistent volume claim (PVC). Create a file, `pvc.yaml`, with the `PersistentVolumeClaim` object definition:
. Define the PVC by creating a `pvc.yaml` file with the `PersistentVolumeClaim` object definition:
+
[source,yaml]
----
Expand Down