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-csi-efs-static-pv.adoc
Olga Tikhomirova 3903bf2d75 OSDOCS-15926 - Removing unused OSD files
(cherry picked from commit d9774fb40a)
2025-11-26 10:02:19 -08:00

43 lines
1.4 KiB
Plaintext

// Module included in the following assemblies:
//
// * storage/persistent_storage/persistent-storage-csi-aws-efs.adoc
// * storage/container_storage_interface/persistent-storage-csi-aws-efs.adoc
:_mod-docs-content-type: PROCEDURE
[id="efs-create-static-pv_{context}"]
= Creating static PVs with Amazon Elastic File Storage
It is possible to use an Amazon Elastic File Storage (Amazon EFS) volume as a single PV without any dynamic provisioning. The whole volume is mounted to pods.
.Prerequisites
* You have created Amazon EFS volumes.
.Procedure
* Create the PV using the following YAML file:
+
[source,yaml]
----
apiVersion: v1
kind: PersistentVolume
metadata:
name: efs-pv
spec:
capacity: <1>
storage: 5Gi
volumeMode: Filesystem
accessModes:
- ReadWriteMany
- ReadWriteOnce
persistentVolumeReclaimPolicy: Retain
csi:
driver: efs.csi.aws.com
volumeHandle: fs-ae66151a <2>
volumeAttributes:
encryptInTransit: "false" <3>
----
<1> `spec.capacity` does not have any meaning and is ignored by the CSI driver. It is used only when binding to a PVC. Applications can store any amount of data to the volume.
<2> `volumeHandle` must be the same ID as the EFS volume you created in AWS. If you are providing your own access point, `volumeHandle` should be ``<EFS volume ID>::<access point ID>``. For example: `fs-6e633ada::fsap-081a1d293f0004630`.
<3> If desired, you can disable encryption in transit. Encryption is enabled by default.