diwangcanada commented on issue #8018:
URL:
https://github.com/apache/incubator-devlake/issues/8018#issuecomment-2347091097
The pvc did not release after uninstall helm chart because of the
protection. This is properly by design, but does it make more sense to set pv
reclaim policy to "retain"?
```
➜ tmp kubectl -n devlake describe pvc devlake-mysql-data-devlake-mysql-0
Name: devlake-mysql-data-devlake-mysql-0
Namespace: devlake
StorageClass: standard
Status: Bound
Volume: pvc-1ebb7410-0e43-460f-af0b-f7d4be573b2a
Labels: app.kubernetes.io/instance=devlake
app.kubernetes.io/name=devlake
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner:
pd.csi.storage.gke.io
volume.kubernetes.io/storage-provisioner:
pd.csi.storage.gke.io
**Finalizers: [kubernetes.io/pvc-protection]**
Capacity: 50Gi
Access Modes: RWO
VolumeMode: Filesystem
Used By: <none>
Events: <none>
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
