Procedure

1. In the graphical installer under Storage Configuration, select Custom → Done to open the dialog for configuring partitions and volumes.
2. Under New Red Hat Enterprise Linux 8.x Installation, select Click here to create them automatically.
3. Select the root partition, /, reduce Desired Capacity so that the VG has sufficient capacity for your PVs, and then click Update Settings.

4. Complete your installation.

   Note

   For more options on partition configuration, see the guide linked in the Additional information section for Configuring Manual Partitioning.

5. As a root user, verify the VG capacity available on your system by running the following command:

   $ sudo vgs

   Example output:

   VG   #PV #LV #SN Attr   VSize    VFree
   rhel   1   2   0 wz--n- <127.00g 54.94g

Procedure

1. As a root user, enable the Red Hat build of MicroShift repositories by running the following command:

   $ sudo subscription-manager repos \
       --enable rhocp-4.12-for-rhel-8-$(uname -i)-rpms \
       --enable fast-datapath-for-rhel-8-$(uname -i)-rpms

2. Install Red Hat build of MicroShift by running the following command:

   $ sudo dnf install -y microshift

3. Download your installation pull secret from the Red Hat Hybrid Cloud Console to a temporary folder, for example, $HOME/openshift-pull-secret. This pull secret allows you to authenticate with the container registries that serve the container images used by Red Hat build of MicroShift.

4. To copy the pull secret to the /etc/crio folder of your RHEL machine, run the following command:

   $ sudo cp $HOME/openshift-pull-secret /etc/crio/openshift-pull-secret

5. Make the root user the owner of the /etc/crio/openshift-pull-secret file by running the following command:

   $ sudo chown root:root /etc/crio/openshift-pull-secret

6. Make the /etc/crio/openshift-pull-secret file readable and writeable by the root user only by running the following command:

   $ sudo chmod 600 /etc/crio/openshift-pull-secret

7. If your RHEL machine has a firewall enabled, you must configure a few mandatory firewall rules. For firewalld, run the following commands:

   $ sudo firewall-cmd --permanent --zone=trusted --add-source=10.42.0.0/16

   $ sudo firewall-cmd --permanent --zone=trusted --add-source=169.254.169.1

   $ sudo firewall-cmd --reload

Procedure

1. As a root user, start the Red Hat build of MicroShift service by entering the following command:

   $ sudo systemctl start microshift

2. Optional: To configure your RHEL machine to start Red Hat build of MicroShift when your machine starts, enter the following command:

   $ sudo systemctl enable microshift

3. Optional: To disable Red Hat build of MicroShift from automatically starting when your machine starts, enter the following command:

   $ sudo systemctl disable microshift

   Note

   The first time that the Red Hat build of MicroShift service starts, it downloads and initializes Red Hat build of MicroShift’s container images. As a result, it can take several minutes for Red Hat build of MicroShift to start the first time that the service is deployed. Boot time is reduced for subsequent starts of the Red Hat build of MicroShift service.

Procedure

1. Enter the following command to stop the Red Hat build of MicroShift service:

   $ sudo systemctl stop microshift

2. Workloads deployed on Red Hat build of MicroShift will continue running even after the Red Hat build of MicroShift service has been stopped. Enter the following command to display running workloads:

   $ sudo crictl ps -a

3. Enter the following commands to stop the deployed workloads:

   $ sudo systemctl stop kubepods.slice

Procedure

1. Enable the Red Hat build of MicroShift RPM repositories on the build host by running the following command:

   $ sudo subscription-manager repos
       --enable rhocp-4.12-for-rhel-8-$(uname -i)-rpms
       --enable fast-datapath-for-rhel-8-$(uname -i)-rpms

2. Install the reposync and createrepo tools by running the following command:

   $ sudo yum install -y yum-utils createrepo

3. Sync the Red Hat build of MicroShift RPM packages to your build host by running the following command:

   $ sudo reposync --arch=$(uname -i) --arch=noarch --gpgcheck \
       --download-path /var/repos/microshift-local \
       --repo=rhocp-4.12-for-rhel-8-$(uname -i)-rpms \
       --repo=fast-datapath-for-rhel-8-$(uname -i)-rpms

4. Remove coreos packages to avoid conflicts by running the following command:

   $ sudo find ${REPO_PATH}/microshift-local -name \*coreos\* -exec rm -f {} \;

5. Create a local RPM repository by running the following command:

   $ sudo createrepo ${REPO_PATH}/microshift-local

6. Create an Image Builder source file for this repository by running the following command:

   $ sudo tee ${REPO_PATH}/microshift-local/microshift.toml > /dev/null <<EOF
   id = "microshift-local"
   name = "MicroShift local repo"
   type = "yum-baseurl"
   url = "file:///${REPO_PATH}/microshift-local/"
   check_gpg = false
   check_ssl = false
   system = false
   EOF

7. Add this source file to Image Builder by running the following command:

   $ sudo composer-cli sources add ${REPO_PATH}/microshift-local/microshift.toml

Prerequisites

1. You have created an RHEL for Edge Installer (ISO) image containing your RHEL for Edge commit with Red Hat build of MicroShift.

2. Create a Kickstart file or use an existing one. In the Kickstart file, you must include:

   1. Detailed instructions about how to create a user.
   2. How to fetch and deploy the RHEL for Edge image.

Procedure

1. In the main section of the Kickstart file, update the setup of the filesystem such that it contains an LVM volume group called rhel with at least 10GB system root. Leave free space for the LVMS CSI driver to use for storing the data for your workloads.

   Example kickstart snippet for configuring the filesystem

   # Partition disk such that it contains an LVM volume group called `rhel` with a
   # 10GB+ system root but leaving free space for the LVMS CSI driver for storing data.
   #
   # For example, a 20GB disk would be partitioned in the following way:
   #
   # NAME          MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
   # sda             8:0    0  20G  0 disk
   # ├─sda1          8:1    0 200M  0 part /boot/efi
   # ├─sda1          8:1    0 800M  0 part /boot
   # └─sda2          8:2    0  19G  0 part
   #  └─rhel-root  253:0    0  10G  0 lvm  /sysroot
   #
   zerombr
   clearpart --all --initlabel
   part /boot/efi --fstype=efi --size=200
   part /boot --fstype=xfs --asprimary --size=800
   # Uncomment this line to add a SWAP partition of the recommended size
   #part swap --fstype=swap --recommended
   part pv.01 --grow
   volgroup rhel pv.01
   logvol / --vgname=rhel --fstype=xfs --size=10000 --name=root

2. In the %post section of the Kickstart file, add your pull secret and the mandatory firewall rules.

   Example Kickstart snippet for adding the pull secret and firewall rules

   %post --log=/var/log/anaconda/post-install.log --erroronfail
   
   # Add the pull secret to CRI-O and set root user-only read/write permissions
   cat > /etc/crio/openshift-pull-secret << EOF
   YOUR_OPENSHIFT_PULL_SECRET_HERE
   EOF
   chmod 600 /etc/crio/openshift-pull-secret
   
   # Configure the firewall with the mandatory rules for MicroShift
   firewall-offline-cmd --zone=trusted --add-source=10.42.0.0/16
   firewall-offline-cmd --zone=trusted --add-source=169.254.169.1
   
   %end

3. Install the mkksiso tool by running the following command:

   $ sudo yum install -y lorax

4. Update the Kickstart file in the ISO with your new Kickstart file by running the following command:

   $ sudo mkksiso <your_kickstart>.ks <your_installer>.iso <updated_installer>.iso