efs-csi-driver addon (v3.1.3): not compatible with Graviton-based clusters

[yellowjung]

Describe the bug

Currently, the efs-csi-driver addon provided by EKS Blueprints does not work properly on Amazon EKS clusters running on Graviton-based (ARM64) instances.

Expected Behavior

The efs-csi-driver addon should deploy and function correctly on ARM64-based EKS clusters.

Current Behavior

The current version of the EKS Blueprints efs-csi-driver addon does not support ARM64 architecture, causing deployment failures or runtime errors.

Reproduction Steps

Steps to reproduce
1. Create an EKS cluster using Graviton-based nodes (ARM64 architecture).
2. Enable and deploy the efs-csi-driver addon via EKS Blueprints.
3. Check the pod status of the efs-csi-driver; pods fail to run properly or enter a CrashLoopBackOff state.

Possible Solution

• I’ve confirmed that upgrading the EFS CSI Driver Helm chart to version 3.1.4 resolves this issue and works correctly on ARM64 (Graviton-based) clusters.
• The current Helm chart version (3.1.3) used by EKS Blueprints references an AWS-managed private ECR image (602401143452.dkr.ecr.ap-northeast-2.amazonaws.com/eks/aws-efs-csi-driver:v2.1.2), which does not provide an ARM64-compatible image.
• Therefore, please either publish an ARM64-compatible version of the above-mentioned AWS-managed ECR image or upgrade the Helm chart version used in EKS Blueprints to 3.1.4 or higher.

Additional Information/Context

No response

CDK CLI Version

2.174.0 (build 9604329)

EKS Blueprints Version

1.16.3

Node.js Version

v22.12.0

Environment details (OS name and version, etc.)

macOS 15.3.1(24D70)

Other information

No response