Vphere's xcopy volume populator is a new experimental copy optimization method.

It should be behind a feature gate, and it needs to be opt-in, probably at the plan level, and

also it is not supported in all cases.( See below)

At the moment the way to trigger an xcopy volume population(on the devel branch https://github.com/rgolangh/forklift/tree/vsphere-xcopy-volume-populator) is to annotate the target plan storage class with "copy-offload: true" . obviously this is not enough, we need far more details, like which data-stores are supported (iscsi or FC) and what is their storage vendors.

The UI behaviour needs to query some kind of a mapping object (a config map?) that will determine if a certain storage mapping could be selected to use "xcopy" and then that should be presented to the user to select.

Caveat with storage mapping here - xcopy depends on the disk being iSCSI or FC in vsphere, and the storage class should be connected to the same storage system. The mapping  itself is not per-disk, so there is no control over which disks should or should not use that method, if its available. in other words - if selected at the plan level, all disks which could be xcopied , would be xcopied