Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement workaround to allow SNO installations for OKD/FCOS #7445

Merged
merged 1 commit into from
Sep 8, 2023

Commits on Aug 24, 2023

  1. Implement workaround to allow SNO installations for OKD/FCOS

    OKD/FCOS uses FCOS as its bootimage, i.e. when booting cluster nodes
    the first time during installation. FCOS does not provide tools such
    as OpenShift Client (oc) or hyperkube which are used during
    single-node cluster installation at first boot (e.g. oc in
    bootkube.sh [0]). RHCOS and SCOS include these tools, but FCOS has to
    pivot the root fs [1] to okd-machine-os [2] first in order to make
    those tools available.
    
    Pivoting uses 'rpm-ostree rebase' but during SNO installation the node
    will be booted from a FCOS Live ISO where the root fs and /sysroot are
    mounted read-only. Thus 'rpm-ostree rebase' fails and necessary tools
    for SNO installation will not be available, causing the setup to stall.
    
    This patch works around this issue by mounting /usr and /etc as
    overlay filesystems which contains both the content of the live iso as
    well as from the okd-machine-os container image.
    
    [0] https://github.com/openshift/installer/blob/master/data/data/bootstrap/files/usr/local/bin/bootkube.sh.template
    [1] https://github.com/openshift/installer/blob/master/data/data/bootstrap/files/usr/local/bin/bootstrap-pivot.sh.template
    [2] https://github.com/openshift/okd-machine-os
    JM1 committed Aug 24, 2023
    Configuration menu
    Copy the full SHA
    ed1467e View commit details
    Browse the repository at this point in the history