Restoring Kubernetes Objects in the Created CCE Cluster

Creating a StorageClass

In this example, the WordPress application uses Alibaba Cloud SSD persistent data volumes, which need to be replaced with HUAWEI CLOUD SSDs.

The StorageClass used in this example is alicloud-disk-ssd. Create an SC with the same name and use HUAWEI CLOUD SSDs as backend storage media. Set this parameter based on the application to migrate.

[root@ccenode-roprr hujun]# cat cce-sc-csidisk-ack.yaml  
allowVolumeExpansion: true 
apiVersion: storage.k8s.io/v1 
kind: StorageClass 
metadata: 
  name: alicloud-disk-ssd 
  selfLink: /apis/storage.k8s.io/v1/storageclasses/csi-disk 
parameters: 
  csi.storage.k8s.io/csi-driver-name: disk.csi.everest.io 
  csi.storage.k8s.io/fstype: ext4 
  everest.io/disk-volume-type: SSD 
  everest.io/passthrough: "true" 
provisioner: everest-csi-provisioner 
reclaimPolicy: Delete 
volumeBindingMode: Immediate  

[root@ccenode-roprr hujun]# kubectl create -f cce-sc-csidisk-ack.yaml

Restoring the Application

[root@ccenode-roprr hujun]# velero restore create --from-backup   wordpress-ack-backup 
Restore request "wordpress-ack-backup-20200707212519" submitted successfully. 
Run `velero restore describe wordpress-ack-backup-20200707212519` or `velero restore logs wordpress-ack-backup-20200707212519` for more details  

[root@ccenode-roprr hujun]# velero restore get 
NAME  BACKUP STATUS  WARNINGS   ERRORS   CREATED SELECTOR 
wordpress-ack-backup-20200708112940   wordpress-ack-backup   Completed   0  02020-07-08 11:29:42 +0800 CST   <none>

Check the running status of the WordPress application. Make adaptation if issues such as image pulling failures and service access failures occur.