aws-efs-csi-driver: driver name efs.csi.aws.com not found in the list of registered CSI drivers

/kind bug

What happened? I was planning to use the EFS CSI driver and installed it to my EKS based on bottlerocket OS according to the guide: https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html with the command as follows: kubectl apply -k “github.com/kubernetes-sigs/aws-efs-csi-driver/deploy/kubernetes/overlays/stable/ecr/?ref=release-1.0” But met one issue like the following in the pods’s logs: Events: Type Reason Age From Message

---

Warning FailedScheduling 48s default-scheduler error while running “VolumeBinding” filter plugin for pod “app1”: pod has unbound immediate PersistentVolumeClaims Warning FailedScheduling 47s default-scheduler error while running “VolumeBinding” filter plugin for pod “app1”: pod has unbound immediate PersistentVolumeClaims Normal Scheduled 40s default-scheduler Successfully assigned default/app1 to ip-192-168-31-184.ec2.internal Warning FailedMount 9s (x7 over 40s) kubelet, ip-192-168-31-184.ec2.internal MountVolume.MountDevice failed for volume “efs-pv” : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name efs.csi.aws.com not found in the list of registered CSI drivers

And I the efs-csi-nod’s status also abnormal: C:\work\iso\CIS\docker>kubectl get pods -n kube-system -o wide | findstr efs efs-csi-node-2scq5 2/3 CrashLoopBackOff 4 111s 192.168.54.201 ip-192-168-54-201.ec2.internal <none> <none> efs-csi-node-8gvxs 2/3 CrashLoopBackOff 5 111s 192.168.31.184 ip-192-168-31-184.ec2.internal <none> <none> efs-csi-node-q49r8 2/3 CrashLoopBackOff 4 111s 192.168.44.14 ip-192-168-44-14.ec2.internal <none> <none> efs-csi-node-s47qb 2/3 CrashLoopBackOff 4 111s 192.168.7.36 ip-192-168-7-36.ec2.internal <none> <none>

more detail errors: C:\work\iso\CIS\docker>kubectl -n kube-system logs -f efs-csi-node-gd2fp -c efs-plugin I1122 12:52:40.834208 1 driver.go:83] Node Service capability for Get Volume Stats Not enabled I1122 12:52:40.861901 1 mount_linux.go:173] Cannot run systemd-run, assuming non-systemd OS I1122 12:52:40.861920 1 mount_linux.go:174] systemd-run failed with: exit status 1 I1122 12:52:40.861930 1 mount_linux.go:175] systemd-run output: I1122 12:52:40.862141 1 driver.go:114] Starting watchdog I1122 12:52:40.862237 1 efs_watch_dog.go:174] Copying /etc/amazon/efs/efs-utils.conf since it doesn’t exist F1122 12:52:40.883887 1 main.go:53] open /etc/amazon/efs/efs-utils.conf: permission denied

What you expected to happen? The efs csi drive is installed successfully and the I can see the efs-csi-nodes installed.

How to reproduce it (as minimally and precisely as possible)? Just do it according to the guide: https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html Anything else we need to know?: PS: i find that the codes in the https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/release-1.0/deploy/kubernetes/base/node.yaml does not change “/etc/amazon/efs” to “/var/amazon/efs” Environment

• Kubernetes version (use kubectl version): C:\work\iso\CIS\docker>kubectl version Client Version: version.Info{Major:“1”, Minor:“19”, GitVersion:“v1.19.0”, GitCommit:“e19964183377d0ec2052d1f1fa930c4d7575bd50”, GitTreeState:“clean”, BuildDate:“2020-08-26T14:30:33Z”, GoVersion:“go1.15”, Compiler:“gc”, Platform:“windows/amd64”} Server Version: version.Info{Major:“1”, Minor:“17+”, GitVersion:“v1.17.9-eks-4c6976”, GitCommit:“4c6976793196d70bc5cd29d56ce5440c9473648e”, GitTreeState:“clean”, BuildDate:“2020-07-17T18:46:04Z”, GoVersion:“go1.13.9”, Compiler:“gc”, Platform:“linux/amd64”}
• Driver version: 1.0