Closed dumlutimuralp closed 2 months ago
i ran into the same issue.
https://github.com/kubernetes-sigs/aws-efs-csi-driver/pull/1323 forgot to change the image.repository
to public.ecr.aws/efs-csi-driver/amazon/aws-efs-csi-driver
.
the tests/qa/ci should've caught this and probably needs to.
I am currently experiencing the same issue as reported. I hope it can be resolved quickly.
Hi, thanks for bringing this to our attention. I've opened a PR that should resolve this. We will work on creating a test to catch this issue in the future.
Hi, @mskanth972
Thank you for the support and the PR addressing the installation issues. I'm pleased to report that the issue has been resolved! By removing and re-adding the Helm repository with the following commands, I was able to successfully deploy the AWS EFS CSI Driver:
$ helm repo remove aws-efs-csi-driver
$ helm repo add aws-efs-csi-driver https://kubernetes-sigs.github.io/aws-efs-csi-driver
This resolved the ImagePullBackOff
errors I was facing. Thanks again for your prompt assistance and dedication to resolving this issue.
Closing the issue as the new helm version(v3.0.2) is able to fix this.
/kind bug
What happened? When I used helm to install EFS CSI Driver I received the following error :
It seems that helm values should be updated with the ECR repository path due to this PR. It still points out to Docker repo (this part in the Helm here)
What you expected to happen? The image to be pulled successfully.
How to reproduce it (as minimally and precisely as possible)? Use helm to install EFS CSI Driver
Anything else we need to know?:
Environment
kubectl version
): Amazon EKS 1.29Please also attach debug logs to help us better diagnose