1
0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 15:47:14 +01:00
Files
installer/docs/dev/pinned-coreos.md
Jonathan Lebon f9f3f67a4d hack/update-rhcos-bootimage.py: update RHCOS_RELEASES_APP
I think this was supposed to be part of #4928.

(cherry picked from commit f9165307f9)
2021-07-20 19:40:27 -04:00

1.9 KiB

CoreOS and the installer

A key decision made before the release of OpenShift 4 is to pin the CoreOS bootimage in the installer: e080f04947

That is still the case today; when one gets an openshift-install binary, that binary contains the 2-tuple (CoreOS, release image), meaning the result of an install will be the same thing each time.

More background:

Stream metadata

As of 4.8 the stream metadata enhancement is in progress which provides a standardized JSON format and injects that data into the cluster as well.

Updating pinned stream metadata

To update the bootimage for one or more architectures, use e.g.

$ plume cosa2stream --target data/data/rhcos-stream.json --distro rhcos  x86_64=48.83.202102230316-0 s390x=47.83.202102090311-0 ppc64le=47.83.202102091015-0 --url https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases

For more information on this command, see:

Updating pinned legacy metadata

To update the legacy metadata, use:

./hack/update-rhcos-bootimage.py https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases/rhcos-4.6/46.82.202008260918-0/x86_64/meta.json amd64

This will hopefully be removed soon.

Origin of stream metadata

For historical reference, the initial file data/data/rhcos-stream.json was generated this way:

$ plume cosa2stream --name rhcos-4.8 --distro rhcos  x86_64=48.83.202102230316-0 s390x=47.83.202102090311-0 ppc64le=47.83.202102091015-0 > data/data/rhcos-stream.json