Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 1. Update options for Red Hat Device Edge
To update Red Hat Device Edge, you can update both Red Hat build of MicroShift and Red Hat Enterprise Linux (RHEL), or each part by itself without updating the other. You must keep the parts in a supported configuration. Consider the following options when planning updates to your current deployments.
1.1. Red Hat Device Edge updates
You can update Red Hat Enterprise Linux (RHEL) operating system independently of your 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
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 | Supported MicroShift Version → Version Updates |
|---|---|---|
| 9.6 | 4.19 | 4.19.0 → 4.19.z |
| 9.4 | 4.18 | 4.18.0 → 4.18.z, 4.18 → 4.19 on RHEL 9.6 |
| 9.4 | 4.17 | 4.17.1 → 4.17.z, 4.17 → 4.18 |
| 9.4 | 4.16 | 4.16.0 → 4.16.z, 4.16 → 4.17, 4.16 → 4.18 |
| 9.2, 9.3 | 4.15 | 4.15.0 → 4.15.z, 4.15 → 4.16 on RHEL 9.4 |
| 9.2, 9.3 | 4.14 | 4.14.0 → 4.14.z, 4.14 → 4.15, 4.14 → 4.16 on RHEL 9.4 |
Keeping component 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 node, or both. For more information, see the Red Hat Device Edge release compatibility matrix.
1.2. Standalone MicroShift updates
You can update just your MicroShift version by embedding the new version in a RHEL image or by installing the RPMs on a standard RHEL operating system. Consider your current operating system version and deployments when planning a MicroShift update.
The following factors apply to a standalone MicroShift version update:
- MicroShift operates as an in-place update and does not require removal of the earlier version.
- Data backups beyond those required for the usual functioning of your applications are not required.
- You can potentially update MicroShift without reinstalling your applications and Operators.
-
Only
rpm-ostreeupdates include automatic rollbacks.
You must update RHEL to update MicroShift if your current operating system is not compatible with the new version of MicroShift that you want to use.
1.2.1. Updating MicroShift on RHEL for Edge
You can have automated backup and system rollback in case any part of the update fails by using the rpm-ostree update path for a new or existing RHEL for Edge deployment.
-
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 an earlier healthy system state if the update fails.
- You do not need to reinstall applications.
- You do not need to reinstall Operators.
- 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 the new version in a RHEL for Edge image, use the procedures in the following documentation:
To understand more about greenboot, see the following documentation:
1.2.2. Manual RPM updates
You can update MicroShift manually on Red Hat Enterprise Linux (RHEL) by updating the RPMs. This type of update is useful for development environments and testing.
- To complete this update type, use the subscription manager to enable the repository that has 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
1.2.2.1. Keeping MicroShift and RHEL in a supported configuration
When using RPM updates, avoid creating an unsupported configuration or breaking your node by carefully managing your RHEL repositories.
Prerequisites
- You understand the support status of the version of MicroShift you are using.
- You have root-user access to your build host.
- You reviewed the Red Hat Device Edge release compatibility matrix.
Procedure
Avoid unintended updates by locking your operating system version by running the following command:
sudo subscription-manager release --set=9.6
$ sudo subscription-manager release --set=9.6Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you are using an EUS MicroShift release, disable the RHEL standard-support-scope repositories by running the following command:
sudo subscription-manager repos \ --disable=rhel-9-for-$(uname -m)-appstream-rpms \ --disable=rhel-9-for-$(uname -m)-baseos-rpms$ sudo subscription-manager repos \ --disable=rhel-9-for-$(uname -m)-appstream-rpms \1 --disable=rhel-9-for-$(uname -m)-baseos-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- You can replace 9 with the major version of your compatible RHEL system if it is not same version given in this example.
After you disable the standard-support repositories, enable the RHEL EUS repos by running the following command:
sudo subscription-manager repos \ --enable rhel-9-for-$(uname -m)-appstream-eus-rpms \ --enable rhel-9-for-$(uname -m)-baseos-eus-rpms$ sudo subscription-manager repos \ --enable rhel-9-for-$(uname -m)-appstream-eus-rpms \1 --enable rhel-9-for-$(uname -m)-baseos-eus-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- You can replace 9 with the major version of your compatible RHEL system if it is not same version given in this example.
Verification
List the repositories you have enabled for RHEL by running the following command:
sudo subscription-manager repos --list-enabled
$ sudo subscription-manager repos --list-enabledCopy to Clipboard Copied! Toggle word wrap Toggle overflow Example output
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.3. Standalone RHEL updates
You can update to any RHEL type without updating MicroShift if the two final versions in your Red Hat Device Edge are compatible. Check compatibilities before beginning an update. Use the RHEL documentation specific to your use case.
For example:
1.4. Simultaneous MicroShift and RHEL updates
You can update your RHEL operating system type and update MicroShift at the same time, if the final versions are a supported configuration of Red Hat Device Edge. You can use following workflow to plan the general steps to take:
- Check for compatibility before beginning an update.
- Use the 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, such as using an RPM installation or embedding MicroShift into an operating system image.
1.5. Migrating MicroShift from RHEL for Edge to image mode for RHEL
Starting with MicroShift 4.19, you can migrate your MicroShift node from RHEL for Edge to image mode for RHEL if the final versions are a supported configuration of Red Hat Device Edge. Check compatibilities before beginning a migration. See the RHEL documentation for instructions to migrate your image-based RHEL system.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}