The assisted service today requires the following configmap:

{
        "4.6": {
                "display_name": "4.6.8",
                "release_image": "quay.io/openshift-release-dev/ocp-release:4.6.8-x86_64",
                "rhcos_image": "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live.x86_64.iso",
                "support_level": "production"
        },
        "4.7": {
                "display_name": "4.7-pre-release",
                "release_image": "quay.io/openshift-release-dev/ocp-release@sha256:2419f9cd3ea9bd114764855653012e305ade2527210d332bfdd6dbdae538bd66",
                "rhcos_image": "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live.x86_64.iso",
                "support_level": "beta"
        }
}

We have agreed that ClusterImageSet will be the source of truth allowing us to leverage existing pipelines in ACM.

support_level is not super important and can be ignored for now. Display name is the clusterimageset name.

The problem is rhcos_image. This cannot be extracted from release image today, nor is it available in any API. (proposed but not implemented)

We believe there is some level of flexibility in which RHCOS image is used, given the early pivot it does to a real image.

Decision was taken that if hive could provide a semver OpenShift release version, internally the assisted service could figure out how to map this to an RHCOS image.

When hive extracts release image and pulls info from it (today this is installer image, oc tools image, etc), it should also pull the semver release.

Ideally I would like this to appear on ClusterImageSet.Status.OpenShiftRelease. However this operation requires a PullSecret, which today are usually associated with each cluster, though we do also support a global pull secret for the entire Hive cluster.

Options:

• use global pull secret if available to extract the release image one time and populate ClusterImageSet.Status.OpenShiftVersion
• wait for a cluster deployment to reference the ClusterImageSet, then perform with it's pull secret. (could mess with internal metrics?)
• leave things as they are, keep doing per cluster jobs to extract info, and add ClusterDeployment.Status.OpenShiftVersion. (careful not to indicate this is the current version, probably needs a rename) This option is likely far easier.

cc atraeger mfilanov