此内容没有您所选择的语言版本。
Chapter 1. Installing from an RPM package
You can install MicroShift from an RPM package on a machine with a supported version of Red Hat Enterprise Linux (RHEL).
1.1. System requirements for installing MicroShift 复制链接链接已复制到粘贴板!
These requirements are the minimum system requirements for MicroShift and RHEL. Add the system requirements for the workload you plan to run.
For example, if an IoT gateway solution requires 4 GB of RAM, your system needs to have at least 2 GB for RHEL and MicroShift, plus 4 GB for the workloads. Thus, this example deployment requires 6 GB of RAM in total.
Allow for extra capacity for future needs if you are deploying physical devices in remote locations. If you are uncertain of the RAM required, use the maximum RAM capacity that the device can support.
The following conditions must be met before installing MicroShift:
A compatible version of Red Hat Enterprise Linux (RHEL). For more information, see the following link:
- AArch64 or x86_64 system architecture.
- 2 CPU cores.
- 2 GB RAM. Installing from the network (UEFI HTTPs or PXE boot) requires 3 GB RAM for RHEL.
- 10 GB of storage.
- You have an active MicroShift subscription on your Red Hat account. If you do not have a subscription, contact your sales representative for more information.
- If your workload requires Persistent Volumes (PVs), you have a Logical Volume Manager (LVM) Volume Group (VG) with enough free capacity for the workloads.
You configure secure access to the system to be able to manage it. For more information, see the following link:
1.2. Compatibility table 复制链接链接已复制到粘贴板!
Plan to pair a supported version of RHEL for Edge with the MicroShift version you are using as described in the following compatibility table:
1.2.1. Red Hat Device Edge release compatibility matrix 复制链接链接已复制到粘贴板!
Red Hat Enterprise Linux (RHEL) and MicroShift work together as a single solution for device-edge computing. You can update each component separately, but the product versions must be compatible.
Supported configurations of Red Hat Device Edge use verified releases for each together as listed in the following table:
| RHEL for Edge Version(s) | MicroShift Version | MicroShift Release Status | Supported MicroShift Version→MicroShift Version Updates |
| 9.4 | 4.16 | Generally Available | 4.16.0→4.16.z, 4.14→4.16 and 4.15→4.16 |
| 9.2, 9.3 | 4.15 | Generally Available | 4.15.0→4.15.z, 4.14→4.15 and 4.15→4.16 |
| 9.2, 9.3 | 4.14 | Generally Available | 4.14.0→4.14.z, 4.14→4.15 and 4.14→4.16 |
| 9.2 | 4.13 | Technology Preview | None |
| 8.7 | 4.12 | Developer Preview | None |
1.3. Before installing MicroShift from an RPM package 复制链接链接已复制到粘贴板!
Preparation of the host machine is recommended before installing MicroShift for memory configuration and FIPS mode.
1.3.1. Configuring volume groups 复制链接链接已复制到粘贴板!
MicroShift uses the logical volume manager storage (LVMS) Container Storage Interface (CSI) plugin for providing storage to persistent volumes (PVs). LVMS relies on the Linux logical volume manager (LVM) to dynamically manage the backing logical volumes (LVs) for PVs. For this reason, your machine must have an LVM volume group (VG) with unused space in which LVMS can create the LVs for your workload’s PVs.
To configure a volume group (VG) that allows LVMS to create the LVs for your workload’s PVs, lower the Desired Size of your root volume during the installation of RHEL. Lowering the size of your root volume allows unallocated space on the disk for additional LVs created by LVMS at runtime.
1.3.2. Prepare for FIPS mode 复制链接链接已复制到粘贴板!
If your use case requires running MicroShift containers in FIPS mode, you must install RHEL with FIPS enabled. After the worker machine is configured to run in FIPS mode, your MicroShift containers are automatically configured to also run in FIPS mode.
Because FIPS must be enabled before the operating system that your node uses starts for the first time, you cannot enable FIPS after you deploy a node.
1.4. Preparing to install MicroShift from an RPM package 复制链接链接已复制到粘贴板!
Configure your Red Hat Enterprise Linux (RHEL) machine to have a logical volume manager (LVM) volume group (VG) with sufficient capacity for the persistent volumes (PVs) of your workload.
Prerequisites
- The system requirements for installing MicroShift have been met.
- You have root user access to your machine.
- You have configured your LVM VG with the capacity needed for the PVs of your workload.
Procedure
-
In the graphical installer under Installation Destination in the Storage Configuration subsection, select Custom
Done to open the dialog for configuring partitions and volumes. The Manual Partitioning window is displayed. - Under New Red Hat Enterprise Linux 9.x Installation, select Click here to create them automatically.
- Select the root partition, /, reduce Desired Capacity so that the VG has sufficient capacity for your PVs, and then click Update Settings.
Complete your installation.
NoteFor more options on partition configuration, read the guide linked in the Additional information section for Configuring Manual Partitioning.
As a root user, verify the VG capacity available on your system by running the following command:
$ sudo vgsExample output:
VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <127.00g 54.94g
Use the following procedure to install Red Hat build of MicroShift from an RPM package.
Prerequisites
- The system requirements for installing Red Hat build of MicroShift have been met.
- You have completed the steps of preparing to install Red Hat build of MicroShift from an RPM package.
Procedure
As a root user, enable the Red Hat build of MicroShift repositories by running the following command:
$ sudo subscription-manager repos \ --enable rhocp-4.16-for-rhel-9-$(uname -m)-rpms \ --enable fast-datapath-for-rhel-9-$(uname -m)-rpmsInstall Red Hat build of MicroShift by running the following command:
$ sudo dnf install -y microshift-
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. To copy the pull secret to the
/etc/criofolder of your RHEL machine, run the following command:$ sudo cp $HOME/openshift-pull-secret /etc/crio/openshift-pull-secretMake the root user the owner of the
/etc/crio/openshift-pull-secretfile by running the following command:$ sudo chown root:root /etc/crio/openshift-pull-secretMake the
/etc/crio/openshift-pull-secretfile readable and writeable by the root user only by running the following command:$ sudo chmod 600 /etc/crio/openshift-pull-secretIf 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
If the Volume Group (VG) that you have prepared for Red Hat build of MicroShift used the default name rhel, no further configuration is necessary. If you have used a different name, or if you want to change more configuration settings, see the Configuring Red Hat build of MicroShift section.