User creates 
MultiNamespaceVirtualMachineStorageMigration and MultiNamespaceVirtualMachineStorageMigrationPlan

Status is only showed per namespace, which makes it hard to wait/watch/monitor the state and the overal result of the Multi Namespace Plan and Migration.

$ oc get MultiNamespaceVirtualMachineStorageMigration -n storage-migration-test-storage-class-migration storage-migration -oyaml
...
status:
  namespaces:
  - completedMigrations:
    - vm-with-instance-type-1769014573-3528829
    name: storage-migration-test-storage-class-migration
    phase: Completed 

4.21.0

Always

$ oc get MultiNamespaceVirtualMachineStorageMigration -n storage-migration-test-storage-class-migration storage-migration -oyaml
apiVersion: migrations.kubevirt.io/v1alpha1
kind: MultiNamespaceVirtualMachineStorageMigration
metadata:
  creationTimestamp: "2026-01-21T16:57:51Z"
  generation: 1
  name: storage-migration
  namespace: storage-migration-test-storage-class-migration
  resourceVersion: "35260331"
  uid: ada086fb-f162-4e37-bb17-8f7388b1dba8
spec:
  multiNamespaceVirtualMachineStorageMigrationPlanRef:
    name: storage-mig-plan
status:
  namespaces:
  - completedMigrations:
    - vm-with-instance-type-1769014573-3528829
    name: storage-migration-test-storage-class-migration
    phase: Completed

-------

$ oc get MultiNamespaceVirtualMachineStorageMigrationPlan -n storage-migration-test-storage-class-migration storage-mig-plan -oyaml
apiVersion: migrations.kubevirt.io/v1alpha1
kind: MultiNamespaceVirtualMachineStorageMigrationPlan
metadata:
  creationTimestamp: "2026-01-21T16:57:50Z"
  generation: 1
  name: storage-mig-plan
  namespace: storage-migration-test-storage-class-migration
  resourceVersion: "35260335"
  uid: d77d7122-3e1b-4010-a2ed-6ef7d14db406
spec:
  namespaces:
  - name: storage-migration-test-storage-class-migration
    virtualMachines:
    - name: vm-with-instance-type-1769014573-3528829
      targetMigrationPVCs:
      - destinationPVC:
          accessModes:
          - Auto
          storageClassName: ocs-storagecluster-ceph-rbd-virtualization
          volumeMode: Auto
        volumeName: dv-disk
status:
  namespaces:
  - completedMigrations:
    - name: vm-with-instance-type-1769014573-3528829
      sourcePVCs:
      - name: fedora-1769014573-338153
        namespace: storage-migration-test-storage-class-migration
        sourcePVC:
          apiVersion: v1
          kind: PersistentVolumeClaim
          metadata: {}
          spec:
            accessModes:
            - ReadWriteOnce
            dataSource:
              apiGroup: cdi.kubevirt.io
              kind: VolumeCloneSource
              name: volume-clone-source-181f2110-52ae-4776-8a36-99ff6b1c343f
            dataSourceRef:
              apiGroup: cdi.kubevirt.io
              kind: VolumeCloneSource
              name: volume-clone-source-181f2110-52ae-4776-8a36-99ff6b1c343f
            resources:
              requests:
                storage: "36194578596"
            storageClassName: hostpath-csi-basic
            volumeMode: Filesystem
            volumeName: pvc-30626fc7-bf05-4eea-8446-fe196f496e3e
          status:
            accessModes:
            - ReadWriteOnce
            capacity:
              storage: 149Gi
            phase: Bound
        volumeName: dv-disk
      targetMigrationPVCs:
      - destinationPVC:
          accessModes:
          - Auto
          name: fedora-1769014573-338153-mig-zz9k
          storageClassName: ocs-storagecluster-ceph-rbd-virtualization
          volumeMode: Auto
        volumeName: dv-disk
    completedOutOf: 1/1
    conditions:
    - category: Required
      lastTransitionTime: "2026-01-21T16:59:00Z"
      message: all storage migrations completed
      status: "False"
      type: Ready
    - category: Required
      lastTransitionTime: "2026-01-21T16:59:00Z"
      message: all storage migrations completed
      status: "False"
      type: Progressing
    - category: Critical
      lastTransitionTime: "2026-01-21T16:59:00Z"
      message: No virtual machines are ready for storage migration
      reason: NotReady
      status: "True"
      type: NotAllVirtualMachinesReady
    name: storage-migration-test-storage-class-migration
    suffix: zz9k

No easy way to see the current state of 
MultiNamespaceVirtualMachineStorageMigration 
and 
MultiNamespaceVirtualMachineStorageMigrationPlan

Unified condition / status / phase for the whole resource, not only per namespace