Description of problem:

Customer wants to know why Red Hat changes hook runner image  from registry.redhat.io/rhmtc/openshift-migration-hook-runner-rhel8  to quay.io in MTV 2.8       

below is the customer Query?

MTV v2.6's manual says to use

registry.redhat.io/rhmtc/openshift-migration-hook-runner-rhel8:v1.8.2-2

as the default hook image,
while MTV v2.8's manual says to use

quay.io/kubev2v/hook-runner

.

registry.redhat.io/rhmtc/openshift-migration-hook-runner-rhel8:v1.8.2-2

is an official image published on

https://catalog.redhat.com/

.
Why did Red Hat decide not to use it?
If

quay.io/kubev2v/hook-runner

is a new one, why doesn't Red Hat register it to

registry.redhat.io

then publish on

https://catalog.redhat.com

?

Version-Release number of selected component (if applicable):

How reproducible:

Always / N%

Steps to Reproduce:

1.
2.
3.

Actual results:

Expected results:

Additional info: