AWS EFS CSI Driver Addon in EKS Cluster - Issue in PVC - PV binding

Question

Background : we are replacing the efs provisioner to AWS EFS CSI Driver.
For that we have created IRSA role with policy(oidc,trusted entity) and addOn on EKS cluster.
Second step: created new storage, PVC with new efs-id
But PVC is in pending state and error message is above one in controller logs.

Errors in EFS Controller logs : 
—————————————————————————————
I0326 09:06:06.820914 1 controller.go:1082] Temporary error received, adding PVC 3f096f7a-9b79-4ad5-bd1c-992c66b73069 to claims in progress 
W0326 09:06:06.820948 1 controller.go:934] Retrying syncing claim "3f096f7a-9b79-4ad5-bd1c-992c66b73069", failure 67 
E0326 09:06:06.820968 1 controller.go:957] error syncing claim "3f096f7a-9b79-4ad5-bd1c-992c66b73069": failed to provision volume with StorageClass "aws-efs-csi-sc-cevoc-dev": rpc error: code = DeadlineExceeded desc = context deadline exceeded 
I0326 09:06:06.820994 1 event.go:298] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"cevoc-1-dev", Name:"efs-claim", UID:"3f096f7a-9b79-4ad5-bd1c-992c66b73069", APIVersion:"v1", ResourceVersion:"119237073", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "aws-efs-csi-sc-cevoc-dev": rpc error: code = DeadlineExceeded desc = context deadline exceeded

Answer

Hi, Siva.
To resolve the `context deadline exceeded` error with the PVC in EFS CSI Driver, follow these steps:

1. **Verify EFS Mount Targets**
   Ensure your EFS file system has mount targets in the same VPC and subnets as your EKS nodes. Check [Mounting EFS file systems](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs.html) for guidance.

2. **Check IAM Roles**
   Confirm that the IAM role associated with the EFS CSI driver has appropriate permissions and the trust relationship includes your EKS cluster’s OIDC identity. Refer to [IAM Roles for Service Accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) for details.

3. **Inspect Security Groups**
   Ensure the security groups for EFS mount targets and EKS nodes allow necessary traffic. The [EFS security group documentation](https://docs.aws.amazon.com/efs/latest/ug/security-considerations.html#network-access) provides relevant information.

4. **Review Storage Class and PVC**
   Check if the `StorageClass` and `PVC` are correctly configured with the EFS file system ID. Misconfiguration here can lead to provisioning failures.

5. **Examine Driver Logs**
   Look at the EFS CSI Driver logs for more specific errors that can hint at the issue's root cause.

6. **Network Configuration**
   Ensure your EKS cluster's network setup allows communication with AWS EFS, including VPC, route tables, and internet/NAT gateways settings.

7. **DNS and Time Sync**
   Verify DNS resolution and time synchronization within your EKS nodes to avoid connectivity and protocol issues.

Addressing these areas should help in resolving the PVC provisioning failure. For more details on troubleshooting, you can refer to the [EFS CSI Driver troubleshooting guide](https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting-efs-csi.html).

Please accept this answer if it helps. Otherwise, feel free to ping me and/or share more details on the itens mentioned above so we can troubleshoot.

Regards,
Pablo Silva

AWS EFS CSI Driver Addon in EKS Cluster - Issue in PVC - PV binding

Relevant content