I have created a Fargate-based EKS cluster v1.20 (the eksctl config is attached), then ran the Helm chart as specified in https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html :
helm repo add aws-efs-csi-driver https://kubernetes-sigs.github.io/aws-efs-csi-driver/
helm repo update
helm upgrade -i aws-efs-csi-driver aws-efs-csi-driver/aws-efs-csi-driver \
--namespace kube-system \
--set image.repository=602401143452.dkr.ecr.us-east-2.amazonaws.com/eks/aws-efs-csi-driver \
--set controller.serviceAccount.create=false \
--set controller.serviceAccount.name=efs-csi-controller-sa
When I run
kubectl get pod -n kube-system -l "app.kubernetes.io/name=aws-efs-csi-driver,app.kubernetes.io/instance=aws-efs-csi-driver"
as recommended by the Helm message, I notice that the efs-csi-controller pods remain in the Pending state forever:
$ kubectl get pod -n kube-system -l "app.kubernetes.io/name=aws-efs-csi-driver,app.kubernetes.io/instance=aws-efs-csi-driver"
NAME READY STATUS RESTARTS AGE
efs-csi-controller-849dc8585-dknlv 0/3 Pending 0 106s
efs-csi-controller-849dc8585-qwz8g 0/3 Pending 0 106s
What am I doing wrong? Is efs-csi-controller not compatible with Fargate?
I'm attaching the cluster config.
fargate_clusterconfig.yaml.txt
I have created a Fargate-based EKS cluster v1.20 (the eksctl config is attached), then ran the Helm chart as specified in https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html :
When I run
kubectl get pod -n kube-system -l "app.kubernetes.io/name=aws-efs-csi-driver,app.kubernetes.io/instance=aws-efs-csi-driver"as recommended by the Helm message, I notice that the efs-csi-controller pods remain in the Pending state forever:
What am I doing wrong? Is efs-csi-controller not compatible with Fargate?
I'm attaching the cluster config.
fargate_clusterconfig.yaml.txt