Docs for OKD 4.18 IPI set up an OCP cluster #2216
Description
Describe the bug
Version: 4.18.0-okd-scos.10
Reproducibility: 100%
Log Bundle: Not applicable
Description:
Following the official OKD 4.18 docs to run a baremetal IPI install results in a (functional) OCP (OpenShift) cluster instead of OKD.
This is likely the case because, in the step Retrieving the OpenShift Installer, a link is constructed which subsequently makes the user download the openshift-baremetal-installer binary for OCP, not OKD.
This also creates a situation where a real pull secret becomes necessary to follow the instructions given. When using the fake pull secret, the subsequent oc adm release extract command fails (unauthorized).
To fix, the RELEASE_IMAGE variable has to be adjusted to point to OKD / Github.
So instead of
export RELEASE_IMAGE=$(curl -s https://mirror.openshift.com/pub/openshift-v4/$RELEASE_ARCH/clients/ocp/$VERSION/release.txt | grep 'Pull From: quay.io' | awk -F ' ' '{print $3}')
One should run
export RELEASE_IMAGE=$(curl -sL https://github.com/okd-project/okd/releases/download/${OKD_VERSION}-okd-scos.${OKD_REVISION}/release.txt | grep 'Pull From: quay.io' | awk -F ' ' '{print $3}')
Where the new variable OKD_VERSION is set to 4.18.0 and OKD_REVISION to a revision of the user's choice (10, in my case).
The pull secret is then no longer required and the later command may be shortened as shown below, removing the reference to the registry config:
oc adm release extract --command=$cmd --to "${extract_dir}" ${RELEASE_IMAGE}
Version
4.18.0-okd-scos.10
Reproducibility
100% when following the docs
Log Bundle
No response