Conversation
Signed-off-by: Rajesh Kumar <rajesh.kumar@suse.com>
|
Tick the box to add this pull request to the merge queue (same as
|
| #### Prerequisites | ||
|
|
||
| - v1.4.0 and later: The controller automatically syncs the virtual machine images with the new cluster, except when a virtual machine image with the same name or display name already exists on the new cluster. | ||
| - v1.4.0 and later: The controller automatically syncs the virtual machine images with the new cluster, along with their associated StorageClasses, except when a virtual machine image with the same name or display name already exists on the new cluster. |
There was a problem hiding this comment.
Not all StorageClass would be synced.
IIUC, only the backing image (vmimage) would be synced.
cc @WebberHuang1118, please correct me if I am wrong.
There was a problem hiding this comment.
Yes, you are right, only the sc related to V1 VMImage. We should provide more detailed context instead of saying that the associated StorageClasses are synced:
- Currently, VM Backup and Restore supports only Longhorn v1 volumes.
- Harvester can automatically back up VMImages to the remote backup target. However, both the backup and restore clusters must be running Harvester v1.4.0 or later. See the prerequisites. In addition, the two clusters should not have VMImages with duplicate names or display names.
- The backup target Refresh Interval setting affects how frequently Harvester discovers existing VMBackups and VMImages from the remote backup target. See Configure Backup Target.
There was a problem hiding this comment.
I am thinking of this rewrite, does it looks okay @WebberHuang1118
v1.4.0 and later: Harvester can automatically back up VMImages to the remote backup target. Both the backup and restore clusters must be running Harvester v1.4.0 or later, and should not have VMImages with duplicate names or display names; sync is skipped for a VMImage if one already exists with the same name or display name. The controller also syncs each VMImage's associated StorageClass. The backup target Refresh Interval setting affects how frequently Harvester discovers existing VMBackups and VMImages from the remote backup target. See Configure Backup Target.
Your first point is already present in the doc
"Backup support is currently limited to Longhorn V1 Data Engine volumes. Harvester is unable to create backups of volumes in external storage."
|
VMI associated storageclass are the one auto-created when we import an image right? The document update is meant to rely that information only. |
WebberHuang1118
left a comment
WebberHuang1118
left a comment
There was a problem hiding this comment.
Thanks for the improvement, please check https://github.com/harvester/docs/pull/1125/changes#r4005984249, thanks.
|
This branch has not been deployed
4 participants
Problem:
The documentation for VM image sync during cluster restore states that the controller automatically syncs virtual machine images to the new cluster, but doesn't mention that each image's associated StorageClass is also synced as part of this process. This omission could lead users to assume StorageClasses need to be manually recreated after a cluster restore.
Solution:
Updated the description to clarify that StorageClasses associated with each virtual machine image are also synced automatically to the new cluster, alongside the image itself. Applied consistently across the current docs and all affected versioned doc snapshots (v1.4–v1.8).
Related Issue(s):
harvester/harvester#11613