Sean Zatz

/ok-to-test

@rajramo61 Thank you for your PR, we will work on reviewing the changes

Hi @benethon , thank you for bringing this to our attention, apologies for the delayed response. I have reproduced this behavior on v1.7.1 of the driver, with k8s v1.28. We...

@eswolinsky3241 Could you please provide `DEBUG` level logs? https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/troubleshooting/README.md Also, how many pods do you add when this issue starts occurring? If there is any other additional information about your...

We are unable to recreate the issue, is there any special stunnel configuration on your ends? v2.X of the driver replaces stunnel with efs-proxy as you mentioned, just wondering whether...

``` [zatzsea@dev-dsk-zatzsea-1a-5f552df4 automationdriver]$ kubectl apply -f storageclass.yaml storageclass.storage.k8s.io/efs-sc created [zatzsea@dev-dsk-zatzsea-1a-5f552df4 automationdriver]$ kubectl apply -f pod.yaml persistentvolumeclaim/efs-claim created pod/efs-app created [zatzsea@dev-dsk-zatzsea-1a-5f552df4 automationdriver]$ kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS...

Does the issue occur every time you attempt to recreate it, or is it something that appears transiently?

My cluster is IPV4, and subnet is IPV4. EFS doesn't support IPV6 currently

Can you run aws ec2 describe-subnets? We have run into customers in the past who had the DNS64 option enabled in their subnets, which caused issues similar to this when...

Please refer to the section "Enable communication with IPv4-only services on the internet with the AWS CLI" and follow the steps listed to allow your cluster to communicate with EFS.