Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[common] Cleanup ReplicationDestinations #29824

Open
2 tasks done
alfi0812 opened this issue Dec 15, 2024 · 0 comments · May be fixed by #29830
Open
2 tasks done

[common] Cleanup ReplicationDestinations #29824

alfi0812 opened this issue Dec 15, 2024 · 0 comments · May be fixed by #29830
Assignees
Labels
enhancement New feature or request

Comments

@alfi0812
Copy link
Collaborator

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

  • 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.
@alfi0812 alfi0812 added the enhancement New feature or request label Dec 15, 2024
@stavros-k stavros-k self-assigned this Dec 15, 2024
@stavros-k stavros-k linked a pull request Dec 21, 2024 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants