Open msftcoderdjw opened 1 month ago
@RemindD to investigate. @Haishi2016 , can you please help to provide the repro steps to @RemindD ?
We leverage pvc and storage class. And storage class will define the reclaim policy. Example in minikube:
apiVersion: v1
items:
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"},"labels":{"addonmanager.kubernetes.io/mode":"EnsureExists"},"name":"standard"},"provisioner":"k8s.io/minikube-hostpath"}
storageclass.kubernetes.io/is-default-class: "true"
creationTimestamp: "2024-10-17T07:06:59Z"
labels:
addonmanager.kubernetes.io/mode: EnsureExists
name: standard
resourceVersion: "257"
uid: 6a375d52-4d38-42db-a01c-05d952e80076
provisioner: k8s.io/minikube-hostpath
reclaimPolicy: Delete
volumeBindingMode: Immediate
kind: List
metadata:
resourceVersion: ""
Reported by @Haishi2016 , seems after uninstall and reinstall, the redis data are not cleaned up, so newly created symphony-api still tries to pick up old jobs.