准备crd资源，从旧集群导出
routetables.gateway.solo.io
kubectl get crd routetables.gateway.solo.io -oyaml >routetables.gateway.solo.io.yaml
下面五个一样操作
upstreamgroups.gloo.solo.io
authconfigs.enterprise.gloo.solo.io
ratelimitconfigs.ratelimit.solo.io
virtualhostoptions.gateway.solo.io
旧的集群上执行备份
| Code Block |
|---|
miniopodname=`kubectl -n zadig get pod -l app=minio|grep -v NAME|awk '{print $1}'`
kubectl -n zadig annotate pod/$miniopodname backup.velero.io/backup-volumes=kr-minio --overwrite
kubectl -n zadig annotate pod/kr-mysql-0 backup.velero.io/backup-volumes=data-kr-mysql-0 --overwrite
kubectl -n zadig annotate pod/kr-mongodb-0 backup.velero.io/backup-volumes=data-kr-mongodb-0 --overwrite
velero backup create zadig-20230717 --include-namespaces zadig |
可以看到备份进度
新的集群上（如果存储类发生变化需要创建以下文件，因为我是从nfs-storage迁移到cephfs-sc）
创建一个声明yaml文件
kubectl create -f routetables.gateway.solo.io.yaml
......
| Code Block |
|---|
vi change-storage-class-config.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: change-storage-class-config
namespace: velero
labels:
velero.io/plugin-config: ""
velero.io/change-storage-class: RestoreItemAction
data:
nfs-storage: cephfs-sc |
kubectl create -f change-storage-class-config.yaml
velero restore create --from-backup zadigbak