We need to document that if the user has a Cluster or Project resource quotas set (https://docs.openshift.com/container-platform/4.17/applications/quotas/quotas-setting-per-project.html). They need to make sure that that they have set enough quota for our pods to do the migration. They can see the defaults below and if necessary they can adjust them, this highly depends on the customer's env. If there are lot of migrations happening at once and the quotas are not set enough for the migrations the migrations can fail. This can also be correlated to the MAX_VM_INFLIGHT which determines how many VMs/disks will be migrated at once.

Defaults which the user can override in the ForkliftController CR:

This affects both cold and warm migrations
For cold migration it might be bit more resource intensive as it does the disk copy, for the warm the users could theoretically reduce the requests.
virt_v2v_container_limits_cpu: "4000m"
virt_v2v_container_limits_memory: "8Gi"
virt_v2v_container_requests_cpu: "1000m"
virt_v2v_container_requests_memory: "1Gi"
_Keep in mind that this affects the v2v requires lot of resources (Compute power and RAM https://libguestfs.org/virt-v2v.1.html)

This affects any migrations with hooks
hooks_container_limits_cpu: "1000m"
hooks_container_limits_memory: "1Gi"
hooks_container_requests_cpu: "100m"
hooks_container_requests_memory: "150Mi"

This affects any OVA migrations
ova_container_limits_cpu: "1000m"
ova_container_limits_memory: "1Gi"
ova_container_requests_cpu: "100m"
ova_container_requests_memory: "150Mi"