How to define tolerations and nodeSelector when executing the migration plan?

[jcorreajr]

Is it possible to define new "tolerations" and "nodeSelectors" for the POD that is created during the execution of the migration plan?

During the execution of the migration plan, a POD running the image: mtv-virt-v2v is created to copy the data.
This POD is initialized with the following "tolerations" and "nodeSelector" settings

  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300

  nodeSelector:
    kubevirt.io/schedulable: "true"

As we use separate "nodes" to run virtual machines, with specific taints, I need to include these taints within the tolerances session of the created PODs.
Is it possible to do that?

[ahadas]

@jcorreajr that's not possible at the moment, but it makes sense to make this configurable - contributions are welcome

[jcorreajr]

Thanks for the quick response. An alternative would be to create a unique MachineSet for migration tasks.