+++ This bug was initially created as a clone of Bug #1981335 +++

Description of problem:
When we try to deploy MTC in a 3.10 cluster the operator reports an error and fail. The logs pod are not created.

Version-Release number of selected component (if applicable):
MTC 1.5.0
AWS 3.10

How reproducible:
Always

Steps to Reproduce:
1. Deploy MTC in a 3.10 cluster

Actual results:
We get this error in the operator pod

^Mfailed: [localhost] (item=migration.openshift.io_directvolumemigrationprogresses.yaml) => {\"ansible_loop_var\": \"item\", \"changed\": false, \"error\": 422
, \"item\": \"migration.openshift.io_directvolumemigrationprogresses.yaml\", \"msg\": \"Failed to create object: b'{\\\"kind\\\":\\\"Status\\\",\\\"apiVersion\
\\":\\\"v1\\\",\\\"metadata\\\":{},\\\"status\\\":\\\"Failure\\\",\\\"message\\\":\\\"CustomResourceDefinition.apiextensions.k8s.io \\\\\\\\\\\"directvolumemig
rationprogresses.migration.openshift.io\\\\\\\\\\\" is invalid: spec.validation.openAPIV3Schema.properties[spec].properties[podSelector].additionalProperties: 
Forbidden: additionalProperties cannot be set to false\\\",\\\"reason\\\":\\\"Invalid\\\",\\\"details\\\":{\\\"name\\\":\\\"directvolumemigrationprogresses.mig
ration.openshift.io\\\",\\\"group\\\":\\\"apiextensions.k8s.io\\\",\\\"kind\\\":\\\"CustomResourceDefinition\\\",\\\"causes\\\":[{\\\"reason\\\":\\\"FieldValue
Forbidden\\\",\\\"message\\\":\\\"Forbidden: additionalProperties cannot be set to false\\\",\\\"field\\\":\\\"spec.validation.openAPIV3Schema.properties[spec]
.properties[podSelector].additionalProperties\\\"}]},\\\"code\\\":422}\\\

And the MTC logs pod are not created. We are not sure if that impacts more resources apart from the logs pods, probably yes.

Expected results:
The deployment should be executed without errors and all MTC pods should be created successfuly and the operator should report no errors.

Additional info:

Attached must-gather.gz