Maybe this bug should be moved to other component, but not installer, if yes, pls feel free to move it.

I believe this is expected and it's the reason that we've been discouraging the use of additional registries in favor of using explicit image references in all places.

Moving to containers team to confirm that this is intentional and if that's so I guess we should treat this as a documentation bug that we should push people to use a fully qualified image format string.

Sorry, to clarify what's happening is that they're creating a pod from an image that's only available from an authenticated registry, in this case "openshift3/ose-docker-registry:v3.7.0-0.176.0".

registry.reg-aws.openshift.com requires authentication and has been added to docker using '--add-registry'

Now, one thing i missed is that they said from the command line 'docker pull openshift3/ose-docker-registry:v3.7.0-0.176.0" works as expected, however when the kubelet attempts to pull the image it doesn't present credentials to the registry unless it uses the fully qualified "registry.reg-aws.openshift.com/openshift3/ose-docker-registry:v3.7.0-0.176.0"

So this might be the kubelet rather than docker?

Agreed, moving to Documentation.

OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed.

[1]: https://access.redhat.com/support/policy/updates/openshift