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
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.6If 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 \1 --disable=rhel-9-for-$(uname -m)-baseos-rpms- 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 \1 --enable rhel-9-for-$(uname -m)-baseos-eus-rpms- 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-enabledExample output
+----------------------------------------------------------+ Available Repositories in /etc/yum.repos.d/redhat.repo +----------------------------------------------------------+ Repo ID: rhel-9-for-x86_64-baseos-eus-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - BaseOS - Extended Update Support (RPMs) Repo URL: https://cdn.redhat.com/content/eus/rhel9/$releasever/x86_64/baseos/os Enabled: 1 Repo ID: rhel-9-for-x86_64-appstream-eus-rpms Repo Name: Red Hat Enterprise Linux 9 for x86_64 - AppStream - Extended Update Support (RPMs) Repo URL: https://cdn.redhat.com/content/eus/rhel9/$releasever/x86_64/appstream/os Enabled: 1
'%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}