Currently for the MTV, we can set transfer network in the provider and in the plan. This will add the secondary network to importer and populator pods using annotation "k8s.v1.cni.cncf.io/networks: ns/<nad-name>".

However, there are cases where the OCP default node network don't have a connectivity to the VMware/RHV providers. So we cannot add the provider directly since forklift controller cannot contact the providers. To solve this, customer have to set IP address on the second interface and enable "routingViaHost" to route the traffic. This requires a cluster wide change. Customer is looking to provide the secondary network to forklift controller pod, just like how it is assigned to the importer/populator pods so that this can be handled within the MTV, instead of changing a cluster wide conf.