Amazon EFS CSI: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
<font color=darkgray>Explain how a pod gets the same file system share all the time.</font> | <font color=darkgray>Explain how a pod gets the same file system share all the time.</font> | ||
=EFS CSI Driver= | |||
Is deployed as a CSIDriver and a DaemonSet. | |||
=Persistent Volume Size= | =Persistent Volume Size= | ||
Revision as of 17:00, 20 August 2020
External
- https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html
- https://github.com/kubernetes-sigs/aws-efs-csi-driver
Internal
Overview
Amazon EFS CSI driver makes possible consuming an EFS file system from an EKS pod via a standard Persistent Volume Claim/Persistent Volume mechanism.
The overall process consists in the following steps:
- Deploy the Amazon EFS CSI driver to an Amazon EKS cluster.
- Provision the EFS file system statically. Only static volume provisioning is supported, which means that the EFS file system must be created outside the EKS cluster before being used.
- Configure a Persistent Volume with the EFS file system ID and deploy it.
- Configure and deploy the corresponding Storage Class
- Configure and deploy the corresponding Persistent Volume Claim.
Explain how a pod gets the same file system share all the time.
EFS CSI Driver
Is deployed as a CSIDriver and a DaemonSet.
Persistent Volume Size
Because Amazon EFS is an elastic file system, it does not enforce any file system capacity limits. The actual storage capacity value in persistent volumes and persistent volume claims is not used when creating the file system. However, since storage capacity is a required field in Kubernetes, it must be specified as a valid value. This value does not limit the size of the Amazon EFS file system.