Adding a node with `oc adm node-image` is unable to pull the release image container and fails to generate the new node ISO.

    100%

    1. Deploy OpenShift cluster with private registry in an offline environment
    2. Create the nodes-config.yaml for new nodes
    3. Run "oc adm node-image create --dir=/tmp/assets
    

    Command fails with error saying that it cannot pull from quay.io/openshift-release-dev/ocp-release@shaXXXXX

    Command generates an ISO used to add the new worker nodes

    When creating the initial agent ISO using "openshift-install agent create image" command, we can see in the output that a sub command is run, "oc adm release extract". When the install-config.yaml contains the ImageContentSourcePolicy section, or ImageDigestMirrorSet section, a flag is added to "oc adm release extract --icsp or idms" which contains the mappings from quay.io to the private registry.

    The oc command does not have a top level icsp or idms flag. The oc adm node-image command needs to have a flag for icsp or idms such that it is able to understand that instead of pulling the release image from quay.io it should pull the image from the private registry.

    Without this flag, the oc command has no way to know that it should be pulling container images from a private registry.