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
There can be more details on what happens when during restore operation there are resource objects exists in cluster and backup both. Would restore copy objects from backup, would restore skip, would restore merge the object
Would Velero restores cluster to backed up state i.e would restore delete objects create after backup
If there are objects in cluster with missing annotations/labels and backup has the same objects, would Velero update the cluster resource objects and add missing annotation/labels. does Velero merges changes from backup to cluster objects. If yes, how does it resolves conflicts
Does Velero checks the API version for the object and does it affects restore operation
What happens if during restore required storage is missing on the target cluster, how does PVs restore affects
Does Velero backup and restore objects not in namespace
The text was updated successfully, but these errors were encountered:
@a-mccarthy I will start this work next week. I am not sure if we have a template for this kind of document, if so, please help to share it. If not, I will try to create the document by following my own idea first then I will send it to you for your review. Thanks.
@a-mccarthy It is ok. The draft doc has been completed and shared.
Please help to review it and compose the official doc based on it. For anything more is required or any question, please just comment on the doc.
Velero documentation does not provide enough details in how restore works https://velero.io/docs/v1.6/how-velero-works/#restores
The text was updated successfully, but these errors were encountered: