Velero can help you port your resources from one cluster to another, as long as you point each Velero instance to the same cloud object storage location. This scenario assumes that your clusters are hosted by the same cloud provider. Note that Velero does not natively support the migration of persistent volumes snapshots across cloud providers. If you would like to migrate volume data between cloud platforms, please enable restic, which will backup volume contents at the filesystem level.
(Cluster 1) Assuming you haven’t already been checkpointing your data with the Velero
schedule operation, you need to first back up your entire cluster (replacing
<BACKUP-NAME> as desired):
velero backup create <BACKUP-NAME>
The default backup retention period, expressed as TTL (time to live), is 30 days (720 hours); you can use the
--ttl <DURATION> flag to change this as necessary. See
how velero works for more information about backup expiry.
(Cluster 2) Configure
VolumeSnapshotLocations, pointing to the locations used by Cluster 1, using
velero backup-location create and
velero snapshot-location create. Make sure to configure the
BackupStorageLocations as read-only
by using the
--access-mode=ReadOnly flag for
velero backup-location create.
(Cluster 2) Make sure that the Velero Backup object is created. Velero resources are synchronized with the backup files in cloud storage.
velero backup describe <BACKUP-NAME>
Note: The default sync interval is 1 minute, so make sure to wait before checking. You can configure this interval with the
--backup-sync-period flag to the Velero server.
(Cluster 2) Once you have confirmed that the right Backup (
<BACKUP-NAME>) is now present, you can restore everything with:
velero restore create --from-backup <BACKUP-NAME>
Check that the second cluster is behaving as expected:
(Cluster 2) Run:
velero restore get
velero restore describe <RESTORE-NAME-FROM-GET-COMMAND>
If you encounter issues, make sure that Velero is running in the same namespace in both clusters.
Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see EnableAPIGroupVersions.