Issue
Admins may see the following warning when describing a pod:Root cause
This warning typically appears only in Elastic Kubernetes Service (EKS) clusters. It’s usually temporary — the Container Storage Interface (CSI) driver is still exposing the file system to the node’s pods. If theFailedMount warnings stop and the volume mounts successfully, the issue is transient and requires no action.
Resolution
IfFailedMount warnings persist and the pod does not mount successfully, follow the steps below.
Step 1: Confirm the EFS CSI driver is registered
Run the following command to check whether theefs.csi.aws.com driver appears in the list of registered CSI drivers:
efs.csi.aws.com appears in the output.
If the driver is not listed, the node may not have been provisioned correctly. Review your EKS node provisioning configuration to confirm the EFS CSI add-on was enabled during cluster or node group setup.
Step 2: Inspect CSI driver pods
Ifefs.csi.aws.com is listed but the mount failure continues, inspect the CSI-related pods across all namespaces:
kube-system namespace in your search. Check both the CSI controller pods and the CSI node pod assigned to the same node as your failing pod.
If you need help, contact Technical Support and include your screenshots, pod descriptions, and logs.