In kubernetes it may happen that you can not get rid of a volumeattachment in deletion status. This situation is strange and should not happen but it happens. In this case can solve this undesired status as followed:
Frist list all existing volumeattachments:
$ kubectl get volumeattachment
copy the name of the volumeattachment causing the problem. Next you can try to delete it with:
$ kubectl delete volumeattachment csi-3a184154fxxxxxxxxxxxxxxxxxxxxx
Test if the volumeattachment was delete successfully.
If not, you can force the deletion by editing the volumeattachment resource itself – run:
$ kubectl edit volumeattachment csi-3a184154fxxxxxxxxxxxxxxxxxxxxx
Search for a section starting with
And delete this lines so that no more ‘finalizers’ section exists. Save and close the editor (in VI this is the command ‘wq!’
Now your volumeattachment should be deleted.
If anybody knows a better solution let me know 😉