Closed kamlad closed 1 year ago
Hi @kamlad, thank you for the issue.
I am not sure it is the goal of the plugin, Can you elaborate on this? Can you provide some more information on the issue. Describe why is it useful or better than current form of backup?
I think that the goal of backup is to have a way to restore you VM after a disaster. To have your disks restored and VM restarted.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
Is this a BUG REPORT or FEATURE REQUEST?:
kind enhancement
What happened:
Looking at documentation and code, it doesn't look like velero kubevirt plugin performs kubevirt VirtualMachineSnapshot before backup
What you expected to happen:
Perform virtual machine snapshot , and then use the snapshots as source of backup
How to reproduce it (as minimally and precisely as possible):
Backup
Anything else we need to know?:
Environment:
kubectl get deployments cdi-deployment -o yaml
):kubectl version
):