You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Volsync Restore is done once with a Manual Trigger. But the PVC and PV corresponding to the Restore arent cleaned up afterwards and are just there for eternity and take about as much space as the running persistence itself
Describe the solution you'd like
Set the corresponding ReplicationDestinations flags to automatically delete the PVCs/PVs after successfull restore.
See: backube/volsync#1388
Describe alternatives you've considered
Manually deleting ReplicationDestinations with kubectl but those will be recreated because of Gitops/Fluxcd.
Additional context
No response
I've read and agree with the following
I've checked all open and closed issues and my request is not there.
I've checked all open and closed pull requests and my request is not there.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Volsync Restore is done once with a Manual Trigger. But the PVC and PV corresponding to the Restore arent cleaned up afterwards and are just there for eternity and take about as much space as the running persistence itself
Describe the solution you'd like
Set the corresponding ReplicationDestinations flags to automatically delete the PVCs/PVs after successfull restore.
See: backube/volsync#1388
Describe alternatives you've considered
Manually deleting ReplicationDestinations with kubectl but those will be recreated because of Gitops/Fluxcd.
Additional context
No response
I've read and agree with the following
The text was updated successfully, but these errors were encountered: