Installer field for image mapping differs from kube object and oc mirror which creates confusing when deploying OpenShift disconnected from the internet

    4.21.2

    100%

    1.Use oc mirror to mirror OCP release content to a private registry
    2.Create install-config.yaml to install cluster

    

    The openshift installer yaml uses the field "imageContentSources" to map container image repos to a private container registry

    oc-mirror creates yaml that looks like the actual kube object, ImageDigestMirrors whiich looks like this:

# from oc-mirror
apiVersion: config.openshift.io/v1
kind: ImageDigestMirrorSet
metadata:
  annotations:
    createdAt: Sunday, 31-Aug-25 13:40:16 UTC
    createdBy: oc-mirror v2
    oc-mirror_version: 4.20.0-202508181603.p2.g830295b.assembly.stream.el9-830295b
  name: idms-release-0
spec:
  imageDigestMirrors:
  - mirrors:
    - ip-10-0-35-196.us-east-2.compute.internal:8443/openshift/release
    source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
  - mirrors:
    - ip-10-0-35-196.us-east-2.compute.internal:8443/openshift/release-images
    source: quay.io/openshift-release-dev/ocp-release
status: {}
####

If we copy the imageDigestMirror section from the oc mirror output into the install-config and try to generate manifests we'll get an error about an unrecognized field and must update the field in the install-config.yaml to "imageDigestSources". This causes customer's confusion as the 2 should align if possible.