이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 1. About Red Hat build of MicroShift updates


Updates are supported on Red Hat build of MicroShift beginning with the General Availability version 4.14. With the 4.16 release, the following updates are supported:

  • A maximum of two minor versions to the next in sequence, for example, from 4.14 to 4.16.
  • One minor version to the next in sequence, for example, from 4.15 to 4.16.
  • Patch updates are also supported from z-stream to z-stream, for example 4.16.1 to 4.16.2.

1.1. Understanding MicroShift updates

Red Hat build of MicroShift updates are supported on both rpm-ostree edge-deployed hosts and non-OSTree hosts. You can complete updates using the following methods:

Note

Only rpm-ostree updates include automatic rollbacks.

1.1.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 must build a new rpm-ostree image and embed the new MicroShift version in that image. The rpm-ostree image can be the same version or an updated version, but the versions of RHEL for Edge and MicroShift must be compatible.

Check following compatibility 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:

Expand

RHEL for Edge Version(s)

MicroShift Version

MicroShift Release Status

Supported MicroShift Version→MicroShift Version Updates

9.4

4.16

Generally Available

4.16.0→4.16.z, 4.14→4.16 and 4.15→4.16

9.2, 9.3

4.15

Generally Available

4.15.0→4.15.z, 4.14→4.15 and 4.15→4.16

9.2, 9.3

4.14

Generally Available

4.14.0→4.14.z, 4.14→4.15 and 4.14→4.16

9.2

4.13

Technology Preview

None

8.7

4.12

Developer Preview

None

1.1.2. Manual RPM updates

You can use the manual RPM update path to replace your existing version of MicroShift. The versions of RHEL and MicroShift must be compatible. Ensuring system health and completing additional system backups are manual processes.

Important

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.

1.1.3. Checking version update path

Before updating MicroShift or {op-system}, determine the compatibilities. Plan for the versions of each that you intend to use.

Red Hat build of MicroShift update paths

MicroShift version 4.16
  • Version 4.16 to 4.16.z on {op-system} or RHEL for Edge 9.4
MicroShift version 4.15
  • Version 4.15 on {op-system} or RHEL for Edge 9.2 or 9.3 to 4.16 on {op-system} or RHEL for Edge 9.4
  • Version 4.15 to 4.15.z on {op-system} or RHEL for Edge 9.2 or 9.3
MicroShift version 4.14
  • Version 4.14 on {op-system} or RHEL for Edge 9.2 or 9.3 to 4.16 on {op-system} or RHEL for Edge 9.4
  • Version 4.14 to 4.15 on {op-system} or RHEL for Edge 9.2 or 9.3
  • Version 4.14 to 4.14.z on {op-system} or RHEL for Edge 9.2 or 9.3
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat