Description of problem: The configuration of the VDDK init image has been moved to the HCO CR. However, there are use cases where this value should be set per disk transfer, like using a specific version of VDDK depending on the VMware source provider. In that situation, it would be great if an annotation could be set on the DataVolume CR and the controller built the Pod spec with the VDDK image set in the annotation, instead of the one configured in HCO.
Flag the bug as RFE and set target release to 4.10 which is the soonest that could make it
As this is the RFE, do we need to create jira card to future follow? Thanks.
Ying, in my opinion, as long as the code merges with functional tests we should be good without the Jira issue.
Arik, is this still relevant?
(In reply to Adam Litke from comment #5) > Arik, is this still relevant? Nope, it's done already (https://github.com/kubevirt/containerized-data-importer/pull/2102)