https://github.com/openshift/doozer/pull/169

The relatedImages syntax is right now.  but the relatedImages are appended to all version(4.1  4.2  4.2-s390x  4.3  4.4).  @jfan, Could you confirm that don't break the 4.1 - 4.2-s390x?

  relatedImages:
    - name: ose-cluster-logging-operator
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-logging-operator@sha256:e51c86bc09baca6a7eb41aa15b71ab18653e5eeb0066ecf816909f70b09b3161
    - name: ose-logging-curator5
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-logging-curator5@sha256:ade99a73a2ac45ec0486302fc32fd4b29c4e4dce47f2a03b3abd5bad8d50d9dc
    - name: ose-logging-elasticsearch5
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-logging-elasticsearch5@sha256:4e32ebcc73eb83e5a55df258df81ccac44dd564fdb1a815fccff80caad21b3d8
    - name: ose-logging-fluentd
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-logging-fluentd@sha256:7b0a835cf3de935f52979f170523fa50617d41cd83c9efbf95cff8f2453197d8
    - name: ose-logging-kibana5
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-logging-kibana5@sha256:95000c76070c3ca62a029a289300336131cfb126af05cdde813f8555d0bc633e
    - name: ose-oauth-proxy
      image: image-registry.openshift-image-registry.svc:5000/openshift/ose-oauth-proxy@sha256:c08ab91628d51823db94c9a5bc05d1ee10ffd7e1f8c65d8f88a9c3fb3c4c9396

The relatedImages spec operators(4.1-4.3) can be installed in OCP 4.1- 4.3 . The installation of operators and registory-pod are ok. But the relatedImages won't work in OCP4.1, 4.2 cluster since the OLM support this function since OCP4.3.