third party BackupItemAction cannot support the VolumePolicy in v1.14.0

[blackpiglet]

Describe the problem/challenge you have

velero/pkg/backup/item_backupper.go

Lines 380 to 397 in 62c7fef

	if groupResource == kuberesource.PersistentVolumeClaims &&
	actionName == csiBIAPluginName {
	snapshotVolume, err := ib.volumeHelperImpl.ShouldPerformSnapshot(obj, kuberesource.PersistentVolumeClaims)
	if err != nil {
	return nil, itemFiles, errors.WithStack(err)
	}
	if !snapshotVolume {
	ib.trackSkippedPV(
	obj,
	kuberesource.PersistentVolumeClaims,
	volumeSnapshotApproach,
	"not satisfy the criteria for VolumePolicy or the legacy snapshot way",
	log,
	)
	continue
	}
	}

Due to this logic check, the VolumePolicy is limited to the Velero CSI BIA, all the other BIA plugins cannot support the VolumePolicy, including the Velero vSphere plugin.

This is a known issue for Velero v1.14.0. The reason is the current BackupItemAction mechanism doesn't have an easy way to let the Velero pass in the VolumePolicy information into the BIA.
The next patch version of v1.14 will give a way to address it.

Describe the solution you'd like

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"