Este contenido no está disponible en el idioma seleccionado.
Chapter 1. Update options with MicroShift and Red Hat Device Edge
Updates are supported on MicroShift beginning with the General Availability version 4.14.
1.1. Red Hat Device Edge updates
You can update Red Hat Enterprise Linux for Edge (RHEL for Edge) images or Red Hat Enterprise Linux (RHEL) with or without updating the MicroShift version if the version combination is supported. See the following table for details:
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 Version(s) |
| MicroShift Version |
| MicroShift Release Status |
| Supported MicroShift Version → Version Updates |
| 9.4 |
| 4.17 |
| Generally Available |
| 4.17.1 → 4.17.z |
| 9.4 |
| 4.16 |
| Generally Available |
| 4.16.0 → 4.16.z, 4.16 → 4.17 |
| 9.2, 9.3 |
| 4.15 |
| Generally Available |
| 4.15.0 → 4.15.z, 4.15 → 4.16 |
| 9.2, 9.3 |
| 4.14 |
| Generally Available |
| 4.14.0 → 4.14.z, 4.14 → 4.15, 4.14 → 4.16 |
1.2. Standalone MicroShift updates
Consider the following when planning to update MicroShift:
- You can potentially update MicroShift without reinstalling your applications and Operators.
- RHEL or RHEL for Edge updates are only required to update MicroShift if the existing operating system is not 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.
1.3. Checking the MicroShift version update path
Before updating MicroShift or RHEL, determine the compatibilities. Plan for the versions of each that you intend to use.
MicroShift update paths
- MicroShift version 4.17
- Version 4.17 → 4.17.z on RHEL 9.4
- MicroShift version 4.16
- Version 4.16 → 4.17 on RHEL 9.4
- Version 4.16 → 4.16.z on RHEL 9.4
- MicroShift version 4.15
- Version 4.15 on RHEL 9.2 or 9.3 → 4.16 on RHEL 9.4
- Version 4.15 → 4.15.z on RHEL 9.2 or 9.3
- MicroShift version 4.14
- Version 4.14 on RHEL 9.2 or 9.3 → 4.16 on RHEL 9.4
- Version 4.14 → 4.15 on RHEL 9.2 or 9.3
- Version 4.14 → 4.14.z on RHEL 9.2 or 9.3
Only rpm-ostree updates include automatic rollbacks.
1.3.1. RPM-OSTree updates
Using the RHEL for Edge rpm-ostree update path allows for automated backup and system rollback in case any part of the update fails.
-
You can update MicroShift on an
rpm-ostreesystem such as RHEL for Edge by building a new system image containing the new version of MicroShift. -
The
rpm-ostreeimage can be the same version or an updated version, but the versions of RHEL for Edge and MicroShift must be compatible.
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.
- Operators 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:
1.3.2. Manual RPM updates
You can update MicroShift manually on a non-OSTree system such as Red Hat Enterprise Linux (RHEL) by updating the RPMs.
- To complete this update type, use the subscription manager to enable the repository that contains the new RPMs.
- Use manual processes to ensure system health and complete additional system backups.
- To begin a manual RPM update, use the procedures in the following documentation:
- About updating MicroShift RPMs manually
Keeping versions in a supported configuration of Red Hat Device Edge can require updating MicroShift and RHEL at the same time. Ensure that your version of RHEL is compatible with the version of MicroShift you are updating to, especially if you are updating MicroShift across two minor versions. Otherwise, you can create an unsupported configuration, break your cluster, or both.
1.4. 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
1.5. 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. Use the following workflow:
- Check for compatibility before beginning an update.
- Use the RHEL for Edge and RHEL documentation specific to your update path to plan and update the operating system.
- Enable the correct MicroShift repository to ensure alignment between your RHEL and MicroShift versions.
- Use the MicroShift update type specific to your update path.
