Create ConfigMap to reference baremetal-installer image

Have CVO maintain a ConfigMap containing the pullspec for the
baremetal-installer container image in the current release image.

We choose the baremetal-installer container because this is the one that
can run inside the cluster - the binary always matches the cpu architecture
of the container and it can run in FIPS mode.

Also include the machine-os-images pullspec in the ConfigMap, for future
flexibility in case it should be needed.

Author: zaneb

images/baremetal/Dockerfile.ci

@@ -19,6 +19,7 @@ RUN DEFAULT_ARCH="$(go env GOHOSTARCH)" hack/build-node-joiner.sh
 
 FROM registry.ci.openshift.org/ocp/4.19:base-rhel9
 
+COPY --from=builder /go/src/github.com/openshift/installer/images/baremetal/manifests /manifests
 COPY --from=builder /go/src/github.com/openshift/installer/bin/openshift-install /bin/openshift-install
 
 RUN dnf upgrade -y && \

images/baremetal/manifests/0000_90_baremetal-installer_01_images.configmap.yaml

@@ -0,0 +1,16 @@
+---
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: installer-images
+  namespace: openshift-config
+  annotations:
+    include.release.openshift.io/ibm-cloud-managed: "true"
+    include.release.openshift.io/self-managed-high-availability: "true"
+    include.release.openshift.io/single-node-developer: "true"
+data:
+  images.json: >
+    {
+      "installer": "registry.ci.openshift.org/openshift:baremetal-installer",
+      "machine-os-images": "registry.ci.openshift.org/openshift:machine-os-images"
+    }

images/baremetal/manifests/image-references

@@ -0,0 +1,12 @@
+kind: ImageStream
+apiVersion: image.openshift.io/v1
+spec:
+  tags:
+  - name: baremetal-installer
+    from:
+      kind: DockerImage
+      name: registry.ci.openshift.org/openshift:baremetal-installer
+  - name: machine-os-images
+    from:
+      kind: DockerImage
+      name: registry.ci.openshift.org/openshift:machine-os-images