Why pv yaml exported from one cluster import to another cluster but the data is empty

General Discussions
1

Asking for help? Comment out what you need so we can get more information to help you!

apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: rook-ceph.rbd.csi.ceph.com
    volume.kubernetes.io/provisioner-deletion-secret-name: rook-csi-rbd-provisioner
    volume.kubernetes.io/provisioner-deletion-secret-namespace: rook-ceph-external
  finalizers:
  - kubernetes.io/pv-protection
  name: pvc-d39014a2-189c-4733-9c0a-b481caa0a860
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 10Mi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: www-web-0
    namespace: default
  csi:
    controllerExpandSecretRef:
      name: rook-csi-rbd-provisioner
      namespace: rook-ceph-external
    driver: rook-ceph.rbd.csi.ceph.com
    fsType: ext4
    nodeStageSecretRef:
      name: rook-csi-rbd-node
      namespace: rook-ceph-external
    volumeAttributes:
      clusterID: rook-ceph-external
      imageFeatures: layering
      imageFormat: "2"
      imageName: csi-vol-8338cc9e-e952-4882-8ca8-6d6716439e8d
      journalPool: replicapool
      pool: replicapool
      storage.kubernetes.io/csiProvisionerIdentity: 1706862929032-9981-rook-ceph.rbd.csi.ceph.com
    volumeHandle: 0001-0012-rook-ceph-external-0000000000000002-8338cc9e-e952-4882-8ca8-6d6716439e8d
  persistentVolumeReclaimPolicy: Delete
  storageClassName: ceph-rbd
  volumeMode: Filesystem
```
### Cluster information:

Kubernetes version:1,28,1
Cloud being used: (put bare-metal if not on a public cloud) 
Installation method:
Host OS: 
CNI and version:
CRI and version: 

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.
2

When you export a PersistentVolume (PV) YAML from one cluster and import it into another, the data appears empty because the PV configuration only includes metadata and access information, not the actual data stored on the backend storage system (like Ceph in your case). The new cluster needs access to the same storage backend and specific volume to access the data, which is not automatically transferred with the PV YAML.