Skip to content
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

Jump to bottom

Update efs-csi-driver.md #1151

Closed
wants to merge 2 commits into from
Closed

Update efs-csi-driver.md #1151

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11a22bb
Update efs-csi-driver.md
parth-pandit Oct 24, 2024
93ef35f
Merge branch 'main' into patch-13
ROunofF Nov 4, 2024
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
2 changes: 1 addition & 1 deletion website/docs/fundamentals/storage/efs/efs-csi-driver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTO
efs-csi-node 3 3 3 3 3 kubernetes.io/os=linux 47s
```

The EFS CSI driver supports both dynamic and static provisioning. For dynamic provisioning, the driver creates an access point for each PersistentVolume, but requires an existing AWS EFS file system that must be specified in the StorageClass parameters. Static provisioning also requires a pre-created AWS EFS file system, which can then be mounted as a volume inside a container using the driver.
The EFS CSI driver supports dynamic and static provisioning. With static provisioning, the storage administrator has to manually create an access point on the pre-provisioned EFS file system and the Kubernetes administrator has to manually create a PV using the EFS access point. However, the dynamic provisioning removes these manual steps. Here, the EFS CSI driver creates a PV and an access point for that PV in the EFS file system automatically once a PVC for that storage class is created. In both the cases, the required network connectivity, the EFS file system and the Kubernetes storage class for that should be pre-provisioned. That's why we have already provisioned an EFS file system, mount targets and the required security group with an inbound rule that allows inbound NFS traffic for your Amazon EFS mount points. Let's retrieve some information about it that will be used later:

An EFS file system has been provisioned for us, along with mount targets and the required security group that includes an inbound rule allowing NFS traffic to the EFS mount points. Let's get its ID which we'll need later:

Expand Down
Loading