velero备份集群，迁移后devops数据未在web显示

Lcz

创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。

操作系统信息
例如：虚拟机/物理机，Centos7.5/Ubuntu18.04，4C/8G

Kubernetes版本信息
1.20.4

容器运行时
20.10

KubeSphere版本信息
kk 安装 3.2.0

问题：我使用velero备份devops流水线的数据后（包括devops-system，命名空间的数据以及local的pv数据，流水线创建的命名空间数据），迁移到新的环境之后，数据恢复，但是web没有具体显示。

排查

1、查看velero恢复日志：velero restore describe workspace-devops-20220108094356

关键信息如下

Cluster: could not restore, customresourcedefinitions.apiextensions.k8s.io "pipelines.devops.kubesphere.io" already exists. Warning: the in-cluster version is different than the backed-up version. Namespaces:

root@sphere-k8s:~# velero restore describe workspace-devops-20220108094356       
Name:         workspace-devops-20220108094356
Namespace:    velero
Labels:       <none>
Annotations:  <none>

Phase:  Completed

Warnings:
  Velero:     <none>
  Cluster:  could not restore, customresourcedefinitions.apiextensions.k8s.io "pipelines.devops.kubesphere.io" already exists. Warning: the in-cluster version is different than the backed-up version.
  Namespaces:
    devops-te899n4:  could not restore, configmaps "istio-ca-root-cert" already exists. Warning: the in-cluster version is different than the backed-up version.
                     could not restore, configmaps "kube-root-ca.crt" already exists. Warning: the in-cluster version is different than the backed-up version.
    test-backup:     could not restore, configmaps "istio-ca-root-cert" already exists. Warning: the in-cluster version is different than the backed-up version.
                     could not restore, configmaps "kube-root-ca.crt" already exists. Warning: the in-cluster version is different than the backed-up version.

Backup:  workspace-devops

Namespaces:
  Included:  all namespaces found in the backup
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        nodes, events, events.events.k8s.io, backups.velero.io, restores.velero.io, resticrepositories.velero.io
  Cluster-scoped:  auto

Namespace mappings:  <none>

Label selector:  <none>

Restore PVs:  auto

2、删除kubesphere-devops-system命名空间，先恢复kubesphere-devops-system数据，再恢复devops-te899n4命名空间数据。

devops-te899n4数据如下。

root@sphere-k8s:~# kubectl describe ns devops-te899n4
Name:         devops-te899n4
Labels:       kubesphere.io/devopsproject=devops-te899n4
              kubesphere.io/namespace=devops-te899n4
Annotations:  kubesphere.io/creator: admin
Status:       Active

No resource quota.

No LimitRange resource.