-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug] Deleting EFS Addon Removes CSIDriver Resource #7518
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Bump. This is still an issue. |
Hi @CrisNevares , you just need to use the
I'll make a small amendment to the docs so this functionality is explained there as-well. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
What were you trying to accomplish?
Add, then remove the
aws-efs-csi-driver
addon in a Fargate-only cluster.Because the
efs.csi.aws.com
CSIDriver resource existed prior to the creation of theaws-efs-csi-driver
addon, I would expect that CSIDriver resource to persist in the cluster if theaws-efs-csi-driver
is added and subsequently removed.What happened?
The
efs.csi.aws.com
CSIDriver resource was deletedHow to reproduce it?
Create a Fargate-only cluster.
Check that the
efs.csi.aws.com
CSIDriver already exists.Create the
aws-efs-csi-driver
addon.Delete the
aws-efs-csi-driver
addon.Notice the
efs.csi.aws.com
CSIDriver has been deleted.Logs
Create an eks-test1 cluster, in order to check default csi drivers:
Check csidriver:
Install aws-efs-csi-driver addon adding this to eks-test1.yml:
I now have efs-csi-controller pods stuck in pending, due to node requirement. But also note the efs csi driver remains intact:
I now remove the addon:
Removes the csidriver, not unexpectedly in retrospect:
Anything else we need to know?
Versions
The text was updated successfully, but these errors were encountered: