-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete PVC do not delete PV and his access point with dynamic provisioning #1382
Comments
Hi @raulgdUOC , Thank you for bringing this issue to our attention. We have investigated the problem where persistent volumes were getting stuck during deletion and have identified the cause. To address this, we recently made updates to the CSI provisioner sidecars and adjusted the RBAC permissions specifically for managing persistent volumes. This should fix the issue. |
Hi @mskanth972, thanks for your response, I have changed the version of the images and updated the ClusterRole, but the problem still persists with the same logs: Show logs controller
Looks like it can't mount the efs at that access point created after delete the PVC and then, it get stucked with the PV in The procedure to test the feature
Am I doing something wrong, or is this procedure not the intended functionality for |
For the above we need to enable this parameter |
I am using I am assigning the parameter |
Hello @mskanth972, The root problem was that when the controller tried to mount the EFS, it couldn't reach the EFS because the Security Group only allowed traffic with the CIDR of my worker nodes. The network of the Pod is different from that of the node, so the controller couldn't mount the EFS or delete the access point and its content, causing it to get stuck in the process. To solve this, I added the label Additionally, the information you provided about the |
/kind bug
What happened?
When I try to delete the PVC, its PV does not get deleted (with
reclaimPolicy: Delete
), and its access point remains. The controller starts to generate logs trying to mount that access point, but it can't mount it.What you expected to happen?
When I delete the PVC, the content inside that PV should be deleted along with its access point.
How to reproduce it (as minimally and precisely as possible)?
I have been using this to deploy the storage class, pod, and PVC -> https://github.com/kubernetes-sigs/aws-efs-csi-driver/tree/master/examples/kubernetes/dynamic_provisioning/specs
I used Helm to deploy it. In the values, the most important change that I made is: controller.deleteAccessPointRootDir=true
Anything else we need to know?:
Environment
kubectl version
): v1.28.9-eksPlease also attach debug logs to help us better diagnose
This is when I create a new PV with the storage class
After delete the POD and the PVC, I start to see this logs:
This is a description of a PV from an another test that I have made. Some parts may not agree with the previous logs. This is the result after delete the PVC.
The text was updated successfully, but these errors were encountered: