Amazon EFS CSI: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 12: Line 12:


Amazon EFS CSI driver makes possible consuming an [[Amazon_Elastic_File_System_Concepts#EFS_File_System|EFS file system]] from an EKS pod via a standard [[Kubernetes_Storage_Concepts#Persistent_Volume_Claim_.28PVC.29|Persistent Volume Claim]]/[[Kubernetes_Storage_Concepts#Persistent_Volume_.28PV.29|Persistent Volume mechanism]].
Amazon EFS CSI driver makes possible consuming an [[Amazon_Elastic_File_System_Concepts#EFS_File_System|EFS file system]] from an EKS pod via a standard [[Kubernetes_Storage_Concepts#Persistent_Volume_Claim_.28PVC.29|Persistent Volume Claim]]/[[Kubernetes_Storage_Concepts#Persistent_Volume_.28PV.29|Persistent Volume mechanism]].
The overall process consists in the following steps:
# 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.
# Deploy the Amazon EFS CSI driver to an Amazon EKS cluster




<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>

Revision as of 02:01, 20 August 2020

External

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:

  1. 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.
  2. Deploy the Amazon EFS CSI driver to an Amazon EKS cluster


Explain how a pod gets the same file system share all the time.