Customer requires to use the short name for a specific deployment as has desconected environment and requires to find the correct private registry on each of their cluster (>150 in diferent locations), then they modified the installation manifest of the operator to just use the short name:

openshift.yaml:          image: dynatrace/dynatrace-operator:v0.11.0
openshift.yaml:          image: dynatrace/dynatrace-operator:v0.11.0

but
 image is still trying to connect to the public redhat registry as there
 is the file "/etc/containers/registries.conf.d/001-rhel-shortnames.conf" specifying an alias for this operator and has precedent:

# grep dynatrace-operator /etc/containers/registries.conf.d/*
/etc/containers/registries.conf.d/001-rhel-shortnames.conf:"dynatrace/dynatrace-operator-bundle-marketplace" = "registry.connect.redhat.com/dynatrace/dynatrace-operator-bundle-marketplace"
/etc/containers/registries.conf.d/001-rhel-shortnames.conf:"dynatrace/dynatrace-operator-bundle" = "registry.redhat.io/dynatrace/dynatrace-operator-bundle"
/etc/containers/registries.conf.d/001-rhel-shortnames.conf:"dynatrace/dynatrace-operator" = "registry.connect.redhat.com/dynatrace/dynatrace-operator"

This file seems not to be present in older versions of OCP, just appeared in OCP 4.12