Open CKnoppas opened 3 weeks ago
@CKnoppas
what's the persistentVolumeReclaimPolicy
value of your pv? this value defines whether csi driver would delete the container when volume is delete, since your pv is created by yourself, the reclaimPolicy: Delete
value in storage class won't take effect
What happened: I am using the driver with static provisioning option following the instructions here https://github.com/kubernetes-sigs/blob-csi-driver/blob/master/deploy/example/e2e_usage.md#static-provisioninguse-an-existing-storage-account
Mounting and writing to the volume is working fine. Each volume created, is generating a blob container in the storage account.
When the PV using the storage class is deleted, the blob container in the storage account does not get deleted.
If i create the azure-cloud-provider secret, deleting the blob containers do** get deleted. https://github.com/kubernetes-sigs/blob-csi-driver/blob/master/docs/read-from-secret.md
What you expected to happen: Deleting of blob containers should work without the azure-cloud-provider secret when using static provisioning as documented here https://github.com/kubernetes-sigs/blob-csi-driver/blob/master/deploy/example/e2e_usage.md#static-provisioninguse-an-existing-storage-account
How to reproduce it: Create a volume in a static storage account with secret ref in the storage class https://github.com/kubernetes-sigs/blob-csi-driver/blob/master/deploy/example/storageclass-blob-secret.yaml
delete the pv + pvc.
Anything else we need to know?: storage class:
Environment: