Last updated
Last updated
To migrate a Cluster from the VKS system to the VKS system, follow the steps in this document.
Perform download helper bash script and grand execute permission for this file ( )
(Optional) Deploy some services to check the correctness of the migration. Suppose, at the source Cluster, I have deployed an nginx service as follows:
Deployment files:
Copy
Now, when you access Node's Public IP, you will see "Hello, MyVNGCloud".
Attention:
For the migration to be successful, on the target Cluster, you need to ensure the following requirements:
The amount of resources needed such as number of nodes, node instance configuration,...
Node labels and node taints are the same as the old cluster.
Corresponding or alternative Storage Class.
Migrating private resources outside cluster (moving private resources outside the cluster) is the process of moving private resources outside the source Cluster to a place that the destination Cluster can use. For example, you may have private resources such as images, databases, etc. Now, before starting to migrate, you need to migrate these resources yourself. For example, if you need:
Migrate Databases: you can use Relational Database Service (RDS) and Object Storage Service (OBS) depending on your needs. After the migration is complete, remember to reconfigure the database for your applications on VKS Cluster.
Migrate Storage: you can use vServer's NFS Server .
Attention:
After you migrate resources outside the Cluster, you need to ensure the target Cluster can connect to these migrated resources.
After you have migrated private resources outside the cluster, you can use the migration tool to backup and restore the application on the source cluster and target cluster.
Create file credentials-velero with the following content:
Install Velero CLI:
Install Velero on your 2 clusters with the command:
Attention:
When you perform a cluster migration from VKS to VKS, we recommend that you use Snapshot to migrate your Volume from the source cluster to the destination cluster.
Install the VNGCloud Snapshot Controller plugin on 2 clusters with the command:
Copy
Annotate the Persistent Volumes that need to be backed up. By default, Velero will not backup volume. You can run the command below to annotate backup of all volumes.
Additionally, you can mark not to backup system resources with the following command:
Apply the file below to create the default VolumeSnapshotClass:
Perform backup according to the syntax:
Perform restore according to the command:
On the VKS system, you need to initialize a Cluster according to the instructions . Make sure that the destination cluster's configuration is the same as the source cluster's configuration.
Migrate Container Images: you can migrate images to VNGCloud Container Registry through instructions .
Create a vStorage Project, Container to receive the cluster's backup data according to instructions .
Create an S3 key corresponding to this vStorage Project according to the instructions .
For example, I have initialized a vStorage Project, Container with the following information: Region: HCM03, Container: mycontainer, Endpoint: .