In case of agent-based OpenShift cluster in a disconnected environment, using `oc adm node-image create` approach to generate discovery ISO for node addition, the oc client always tries to contact quay first instead of using the mirror/internal registry as reference because of the nature that oc uses ICSPOnErrorStrategy.

For environments with strict firewall restrictions where the outside connectivity is completely forbidden, due to this policy, even though the node-joiner pod runs and takes all the reference from ICSP/IDMS of the cluster, a connection failure to quay.io just hangs the process instead of falling back to mirror registry. 

4.18.23

OpenShift agent-based cluster in a disconnected environment     

The node-joiner process hangs and ISO couldn't be generated    

The oc client should be able to create the ISO with all the references from the ICSP/IDMS