Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Update options with Red Hat build of MicroShift and Red Hat Device Edge
You can update Red Hat Enterprise Linux for Edge (RHEL for Edge) images or Red Hat Enterprise Linux (RHEL) with or without updating the Red Hat build of MicroShift version if the version combination is supported. See the following table for details:
Red Hat Device Edge release compatibility matrix
The two products of Red Hat Device Edge work together as a single solution for device-edge computing. To successfully pair your products, use the verified releases together for each as listed in the following table:
| RHEL for Edge Version(s) | MicroShift Version | MicroShift Release Status | MicroShift Supported Updates |
| 9.2, 9.3 | 4.15 | Generally Available | 4.15.0→4.15.z and 4.15→future minor version |
| 9.2, 9.3 | 4.14 | Generally Available | 4.14.0→4.14.z and 4.14→4.15 |
| 9.2 | 4.13 | Technology Preview | None |
| 8.7 | 4.12 | Developer Preview | None |
2.1. Checking version update path
Before attempting an update of either Red Hat Device Edge component, determine which versions of MicroShift and RHEL for Edge or RHEL are installed. Plan for the versions of each that you intend to use.
Red Hat build of MicroShift update paths
- Generally Available Version 4.14 to 4.14.z or 4.15 on RHEL for Edge 9.2 or 9.3
- Generally Available Version 4.14 to 4.14.z or 4.15 on RHEL 9.2 or 9.3
- Generally Available Version 4.15 to 4.15.z on RHEL for Edge 9.2 or 9.3
- Generally Available Version 4.15 to 4.15.z on RHEL 9.2 or 9.3
Updates of MicroShift from one minor version to the next must be in sequence. For example, you cannot update from 4.14 to 4.16. You must update 4.14 to 4.15 and so on.
2.2. Standalone MicroShift updates
You can update MicroShift without reinstalling your applications. RHEL or RHEL for Edge updates are also not required to update MicroShift, as long as the existing operating system is compatible with the new version of MicroShift that you want to use.
MicroShift operates as an in-place update and does not require removal of the previous version. Data backups beyond those required for the usual functioning of your applications are also not required.
2.2.1. RPM-OSTree updates
You can update MicroShift on an rpm-ostree system such as RHEL for Edge by building a new image containing the new version of MicroShift. Ensure that the version of the operating system you want to use is compatible with the new version of MicroShift that you update to.
The following features are available in the RHEL for Edge update path:
- The system automatically rolls back to a previous healthy system state if the update fails.
- Applications do not need to be reinstalled.
- You can update an application without updating MicroShift using this update type.
- The image you build can contain other updates as needed.
To begin a MicroShift update by embedding in a RHEL for Edge image, use the procedures in the following documentation:
To understand more about Greenboot, see the following documentation:
2.2.2. Manual RPM updates
You can update MicroShift manually on a non-OSTree system such as Red Hat Enterprise Linux (RHEL) by downloading and updating the RPMs. To complete this update type, use the subscription manager to access the repository containing the new RPMs. To begin a manual RPM update, use the procedures in the following documentation:
2.3. Standalone RHEL for Edge updates
You can update RHEL for Edge or RHEL without updating MicroShift, on the condition that the two versions are compatible. Check compatibilities before beginning an update. Use the RHEL for Edge documentation specific to your update path.
Additional resources
2.4. Simultaneous MicroShift and operating system updates
You can update RHEL for Edge or RHEL and update MicroShift at the same time, on the condition that the versions are compatible. Check for compatibility before beginning an update. First use the RHEL for Edge and RHEL documentation specific to your update path to plan and update the operating system. Then use the MicroShift update type specific to your update path.
