PersistentVolumes and PersistentVolumeClaims persist even after helm uninstall #1477
Description
Hi,
We started encountering a problem where open-match couldn't start successfully. After digging around we found that the redis data volumes are never reset, even after making many changes and uninstalling from helm many times. This meant we had millions of tickets in redis upon start-up. Example:
redis-data-open-match-redis-node-0 Bound pvc-c94f7e4b-4543-4e8d-985e-cee49710e32b 8Gi RWO standard 115d
redis-data-open-match-redis-node-1 Bound pvc-3af3f3f5-d29d-4b0e-808d-a1fedc3304db 8Gi RWO standard 115d
redis-data-open-match-redis-node-2 Bound pvc-146917d1-ceab-4331-9163-01807a19290f 8Gi RWO standard 8d
and
pvc-359a9f92-996f-4ee1-ba42-539a497c0a1c 8Gi RWO Delete Bound open-match/redis-data-open-match-redis-node-1 standard 27d
pvc-a934b590-70bf-47b9-bd9c-e6f3ec186fec 8Gi RWO Delete Bound open-match/redis-data-open-match-redis-node-2 standard 6d19h
pvc-f9bb0538-0b30-4d84-8bbc-6d3f604b985f 8Gi RWO Delete Bound open-match/redis-data-open-match-redis-node-0 standard 27d
It is unexpected that any data would remain after installing.