My default storage class has was setup with reclaimPolicy: Retain.
Everytime Kasten exports backups, it will create copy-vol* pods which request kanister-pvc’s with the same storage class as what they are copying. This means that everytime a 20G volume is backed up, a new 20G PV is requested and used up. This quickly leads to running out of storage.
I’ve already set up kasten 4.5.9 with a storage class that has “reclaimPolicy: Delete”, but since it the copy-vol containers seem to mirror the SC of existing PVs that doesn’t help.
Is there anyway to prevent the PV buildup as a result of backups? For now I’m manually patching all released PVs with “reclaimPolicy: Delete”.
Best answer by jaiganeshjk
View original