You can update {op-system-ostree-first} images or {op-system-base-full} with or without updating the {product-title} version if the version combination is supported. See the following table for details:
|
Important
|
Updates of {microshift-short} are supported with a maximum of two minor versions. For example, you can update from 4.14 to 4.16 in a single step. Updating 4.14 to 4.15 first is not required. |
Consider the following when planning to update {microshift-short}:
-
You can potentially update {microshift-short} without reinstalling your applications and Operators.
-
{op-system} or {op-system-ostree} updates are only required to update {microshift-short} if the existing operating system is not compatible with the new version of {microshift-short} that you want to use.
-
{microshift-short} 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.
You can update {microshift-short} on an rpm-ostree system such as {op-system-ostree} by building a new image containing the new version of {microshift-short}. Ensure that the version of the operating system you want to use is compatible with the new version of {microshift-short} that you update to.
The following features are available in the {op-system-ostree} 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-short} using this update type.
-
The image you build can contain other updates as needed.
To begin a {microshift-short} update by embedding in a {op-system-ostree} image, use the procedures in the following documentation:
To understand more about Greenboot, see the following documentation:
You can update {microshift-short} manually on a non-OSTree system such as {op-system-base-full} 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:
You can update {op-system-ostree} or {op-system} without updating {microshift-short}, on the condition that the two versions are compatible. Check compatibilities before beginning an update. Use the {op-system-ostree} documentation specific to your update path.
You can update {op-system-ostree} or {op-system} and update {microshift-short} at the same time, on the condition that the versions are compatible. Check for compatibility before beginning an update. First use the {op-system-ostree} and {op-system} documentation specific to your update path to plan and update the operating system. Then use the {microshift-short} update type specific to your update path.