diwangcanada commented on issue #8018:
URL:
https://github.com/apache/incubator-devlake/issues/8018#issuecomment-2348899980
Compare pvc for mysql vs grafana, I see grafana pvc has additional labels
and annotations.
Is this the reason mysql pvc was not cleaned up?
```
➜ tmp kubectl -n devlake describe pvc devlake-grafana
Name: devlake-grafana
Namespace: devlake
StorageClass: standard
Status: Bound
Volume: pvc-83fbb87d-8539-48d1-bc73-63038531f8ec
Labels: app.kubernetes.io/instance=devlake
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=grafana
app.kubernetes.io/version=v1.0.1-beta9
helm.sh/chart=grafana-6.56.6
Annotations: **meta.helm.sh/release-name: devlake
meta.helm.sh/release-namespace: devlake**
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]
.....
```
```
➜ 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-b7917694-1d8f-4bf8-9242-92e8576edbc5
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
.....
```
--
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]
