You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues with deletion of the manual PV after the respective PVC got deleted (because the pod got deleted).
I set persistentVolumeReclaimPolicy: Delete so that the deletion of the pod automatically frees all resources. But it fails at the PV.
# Statically provisioned PVC:# An existing bucket or path inside bucket manually created# by the administrator beforehand will be bound to the PVC,# and it won't be removed when you remove the PVapiVersion: v1kind: PersistentVolumemetadata:
name: csi-s3-manual# cluster wide object, no namespacespec:
storageClassName: csi-s3capacity:
storage: 10GiaccessModes:
- ReadWriteOnceclaimRef:
namespace: mynamespacename: csi-s3-manual-pvcpersistentVolumeReclaimPolicy: Deletecsi:
driver: ru.yandex.s3.csicontrollerPublishSecretRef:
name: csi-s3-secretnamespace: kube-systemnodePublishSecretRef:
name: csi-s3-secretnamespace: kube-systemnodeStageSecretRef:
name: csi-s3-secretnamespace: kube-systemvolumeAttributes:
capacity: 10Gimounter: geesefsoptions: --memory-limit 1000 --dir-mode 0777 --file-mode 0666volumeHandle: mybucket/mypath
kubectl describe shows the following Event
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning VolumeFailedDelete 37s persistentvolume-controller error getting deleter volume plugin for volume "csi-s3-manual": no deletable volume plugin matched
Any help or fix is highly appreciated.
The text was updated successfully, but these errors were encountered:
Hi there,
I am having issues with deletion of the manual PV after the respective PVC got deleted (because the pod got deleted).
I set
persistentVolumeReclaimPolicy: Delete
so that the deletion of the pod automatically frees all resources. But it fails at the PV.kubectl describe shows the following Event
Any help or fix is highly appreciated.
The text was updated successfully, but these errors were encountered: