kubevirt-dm: Velero Upstream Changes (Policy Actions)

[weshayutin]

Velero Upstream Changes (Policy Actions)

• upstream and or cherry-picked to openshift/velero or carried.

Description:
Allow unrecognized volume policy actions (such as "kubevirt"). Velero should just not do fs-backup or snapshotting for unrecognized actions rather than erroring out.

Subtasks:

DOD:

[shubham-pampattiwar]

Testing Observations from kubevirt-datamover-controller Phase 1

During Phase 1 testing of the kubevirt-datamover-controller, we observed behavior that validates the need for upstream changes:

Current Behavior

When creating a DataUpload with datamover: kubevirt, Velero's DataUpload controller still reconciles it and fails with:

message: 'not exist type of exposer: csi type of snapshot exposer is not exist'
phase: Failed

Our kubevirt-datamover-controller receives the reconcile event (predicate filter for datamover: kubevirt works), but Velero's controller wins the race and sets the status to Failed first.

What's Needed

Velero's DataUpload controller should skip reconciling entirely when spec.datamover is set to a value it doesn't handle (e.g., "kubevirt"). This allows the external datamover controller to own the full lifecycle of those DataUpload CRs.

Similar logic should apply to DataDownload for restore flows.

cc @sseago