Chapter 1. Red Hat build of MicroShift 4.22 release notes


Red Hat build of MicroShift (MicroShift) provides developers and IT organizations with small-form-factor and edge computing delivered as an application that customers can deploy on top of their managed Red Hat Enterprise Linux (RHEL) devices at the edge. Built on OpenShift Container Platform and Kubernetes, MicroShift provides an efficient way to operate a single node in low-resource edge environments.

1.1. About this release

Built on OpenShift Container Platform and Kubernetes, MicroShift provides an efficient way to operate a single node in low-resource edge environments.

MicroShift is designed to make control plane restarts economical and be lifecycle-managed as a single unit by the operating system. Updates, roll-backs, and configuration changes consist of simply staging another version in parallel and then - without relying on a network - flipping to and from that version and restarting.

Version 4.22 of MicroShift includes new features and enhancements. Update to the latest version of MicroShift to receive all of the latest features, bug fixes, and security updates. MicroShift is derived from OpenShift Container Platform 4.22 and uses the CRI-O container runtime. New features, changes, and known issues that pertain to MicroShift are included in this topic.

You can deploy a MicroShift node to on-premise, cloud, disconnected, and offline environments.

MicroShift 4.22 is supported on Red Hat Enterprise Linux (RHEL) 9.8.

For lifecycle information, see the Red Hat build of MicroShift Life Cycle Policy.

1.2. New features and enhancements

This release adds improvements related to the following components and concepts.

With this release, MicroShift is supported on Red Hat Enterprise Linux (RHEL) 9.8.

1.2.2. Ingress TLS configuration documentation

With this release, MicroShift documentation adds procedures and prerequisites for the default ingress router certificate (ingress.certificateSecret) and for TLS on Kubernetes Ingress objects.

1.3. Technology Preview features

Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:

Technology Preview Features Support Scope

Red Hat Enterprise Linux (RHEL) 10.2 is available as a Technology Preview feature with MicroShift 4.22.

1.4. Known issues

Understand the known issues that impact your MicroShift development and deployments.

  • The following known issues exist for MicroShift RPM installation failures on Red Hat Enterprise Linux (RHEL) 10.1, requiring manual installation:

    • MicroShift RPMs are not available from RHEL 10 repositories.
    • RHEL 9 repositories cannot be enabled with a subscription-manager agent on RHEL 10.
    • Manual single-RPM installation fails with missing dependencies.
Note

To resolve this issue, follow these steps to use entitlement certificates to create the RHEL Content Delivery Network (CDN) repository files in the /etc/yum.repos.d/ directory, and reinstall MicroShift.

  1. Navigate to the /etc/yum.repos.d/ directory.
  2. Create the rhocp-4.21.repo repository for MicroShift packages by entering the following information:

    $ CERT=$(ls /etc/pki/entitlement/[0-9]*.pem | grep -v "-key.pem" | head -n1)
    $ KEY=$(ls /etc/pki/entitlement/[0-9]*-key.pem | head -n1)
    
    $ cat <<EOF | sudo tee /etc/yum.repos.d/rhocp-4.21.repo
    [rhocp-4.21]
    name=Red Hat OpenShift 4.21 for RHEL 9
    baseurl=https://cdn.redhat.com/content/dist/layered/rhel9/x86_64/rhocp/4.21/os
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
    sslverify=1
    sslcacert=/etc/rhsm/ca/redhat-uep.pem
    sslclientcert=$CERT
    sslclientkey=$KEY
    EOF
  3. Create the fast-datapath.repo repository for Fast Datapath packages by entering the following information:Expand commentComment on line R38Resolved

    $ CERT=$(ls /etc/pki/entitlement/[0-9]*.pem | grep -v "-key.pem" | head -n1)
    $ KEY=$(ls /etc/pki/entitlement/[0-9]*-key.pem | head -n1)
    
    $ cat <<EOF | sudo tee /etc/yum.repos.d/fast-datapath.repo
    [fast-datapath]
    name=Red Hat Fast Datapath for RHEL 9
    baseurl=https://cdn.redhat.com/content/dist/layered/rhel9/x86_64/fast-datapath/os
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
    sslverify=1
    sslcacert=/etc/rhsm/ca/redhat-uep.pem
    sslclientcert=$CERT
    sslclientkey=$KEY
    EOF
  4. Install MicroShift using the new repository information.

    $ dnf install microshift

1.5. Additional release notes

Release notes for related components and products are available in the following documentation:

1.5.1. GitOps release notes

See Red Hat OpenShift GitOps: Highlights of what is new and what has changed with this OpenShift GitOps release for more information. You can also go to the following Red Hat package download page and search for "gitops" if you just need the latest package: Red Hat packages.

1.5.2. OpenShift Container Platform release notes

See the OpenShift Container Platform Release Notes for information about the Operator Lifecycle Manager and other components. Not all of the changes to OpenShift Container Platform apply to MicroShift. See the specific MicroShift implementation of an Operator or function for more information.

See the Release Notes for Red Hat Enterprise Linux 10 for more information about RHEL.

See the Release notes for more information about Red Hat OpenShift AI Self-Managed.

1.6. Asynchronous updates

Security, bug fix, and enhancement updates for MicroShift 4.22 are released asynchronously through the Red Hat Network. All MicroShift 4.22 updates are available on the Red Hat Customer Portal. For more information about asynchronous updates, read the MicroShift Life Cycle.

Red Hat Customer Portal users can enable update notifications in the account settings for Red Hat Subscription Management (RHSM). When notifications are enabled, you are notified through email whenever new updates relevant to your registered systems are released.

Note

Red Hat Customer Portal user accounts must have systems registered and consuming MicroShift entitlements for MicroShift update notification emails to generate.

This section is updated over time to provide notes on enhancements and bug fixes for future asynchronous releases of MicroShift 4.22. Versioned asynchronous releases, for example with the form MicroShift 4.22.z, are detailed in the following subsections.

Issued: 08 September 2026. Review the changes in this MicroShift update. Use the advisory links and image lists to see what is fixed and to plan how you apply the update to your deployment.

Red Hat build of MicroShift release 4.22.13 is now available. Fixed issues are listed in the RHSA-2026:63639 advisory. Release notes for fixed issues are provided in this documentation. The images that are included in the update are provided by the OpenShift Container Platform RHSA-2026:63096 advisory.

See the latest images included with MicroShift by using the following instructions:

1.6.1.1. Fixed issues

There are no notable fixed issues in this release.

Issued: 30 July 2026. Review the changes in this MicroShift update. Use the advisory links and image lists to see what is fixed and to plan how you apply the update to your deployment.

Red Hat build of MicroShift release 4.22.7 is now available. Fixed issues are listed in the RHBA-2026:45112 advisory. Release notes for fixed issues are provided in this documentation. The images that are included in the update are provided by the OpenShift Container Platform RHSA-2026:44237 advisory.

See the latest images included with MicroShift by using the following instructions:

1.6.2.1. Fixed issues

  • Before this release, MicroShift did not support Cluster to Cluster Communication (C2CC), limiting the ability to establish direct connectivity between MicroShift clusters at the edge. With this release, the C2CC feature is available as a Technology Preview in MicroShift 4.22, enabling cluster-to-cluster networking for edge deployments. This backport includes the full feature implementation with code and tests. (OCPBUGS-99419)
  • Before this release, MicroShift did not support custom DNS configuration, which required users to rely on the default DNS settings without the ability to tailor name resolution to their specific edge environment. With this release, custom DNS configuration is available in MicroShift 4.22, and allows administrators to customize DNS behavior to meet site-specific requirements. This backport includes the full feature implementation with code and tests. (OCPBUGS-99406)

1.6.2.2. Known issues

  • MicroShift 4.22.7 images have a prioritizer compatibility issue with unsupported paths that lead to an incomplete fixed issue in the release notes. There is no workaround for OCPBUGS-98603. As a result, users should apply a system update to resolve the issue. (OCPBUGS-99904)

Issued: 09 July 2026. Review the changes in this MicroShift update. Use the advisory links and image lists to see what is fixed and to plan how you apply the update to your deployment.

Red Hat build of MicroShift release 4.22.4 is now available. Fixed issues are listed in the RHBA-2026:35330 advisory. Release notes for fixed issues are provided in this documentation. The images that are included in the update are provided by the OpenShift Container Platform RHSA-2026:34794 advisory.

See the latest images included with MicroShift by using the following instructions:

1.6.3.1. Fixed issues

There are no notable fixed issues in this release.

Issued: 30 June 2026. Review the changes in this MicroShift update. Use the advisory links and image lists to see what is fixed and to plan how you apply the update to your deployment.

Red Hat build of MicroShift release 4.22.3 is now available. Fixed issues are listed in the RHBA-2026:29956 advisory. Release notes for fixed issues are provided in this documentation. The images that are included in the update are provided by the OpenShift Container Platform RHBA-2026:29797 advisory.

See the latest images included with MicroShift by using the following instructions:

1.6.4.1. Fixed issues

There are no notable fixed issues in this release.

Issued: 09 June 2026. Review the changes in this MicroShift update. Use the advisory links and image lists to see what is fixed and to plan how you apply the update to your deployment.

Red Hat build of MicroShift release 4.22.0 is now available. Bug fixes and enhancements are listed in the RHEA-2026:2640 advisory. Release notes for bug fixes and enhancements are provided in this documentation. The images that are included in the update are provided by the OpenShift Container Platform RHBA-2026:449 advisory.

See the latest images included with MicroShift by using the following instructions:

1.6.5.1. Enhancement

  • With this release, the MicroShift certificate manager container images now reference platform-specific digests instead of multi-platform manifest lists. (OCPBUGS-66414)
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top