Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 1. Red Hat build of MicroShift 4.19 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
Copy link

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.19 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.19 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.19 is supported on Red Hat Enterprise Linux (RHEL) 9.6.

Updates for both single-version minor releases and patch releases are supported. See Update options with Red Hat build of MicroShift and Red Hat Device Edge for details.

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

1.2. New features and enhancements
Copy link

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

1.2.1. RHEL image mode (Generally Available)
Copy link

Installing MicroShift by using a bootc container image is now generally available. Previously available as a Technology Preview feature, image mode for RHEL is a deployment method that uses a container-native approach to build, deploy, and manage the operating system as a rhel-bootc container image. See Understanding image mode for RHEL with MicroShift for more information.

With this release, the ingress.certificate.Secret,ingress.clientTLS, ingress.routeAdmissionPolicy, and ingress.tlsSecurityProfile parameters are added to the YAML configuration file for MicroShift. These parameters specify security settings for the ingress controller. For more information, see Using ingress control for a MicroShift node.

1.2.3. MicroShift control plane enhanced with TLS
Copy link

With this release, configurable transport layer security (TLS) protocols on internal control plane components are enabled to help prevent known insecure protocols, ciphers, or algorithms from accessing the applications you run on MicroShift. You use either the TLS 1.2 or TLS 1.3 with MicroShift. For more information, see Configuring TLS security profiles.

With this release, you can use the microshift healthcheck command with various options to run a basic health check on your applications. For more information, see Greenboot workload health checks.

With this release, you can configure the MicroShift Observability service to collect performance and usage metrics for monitoring resources. The following predefined configurations differ in the amount of data collected:

  • Small
  • Medium
  • Large (default)

For more information, see Using MicroShift Observability.

1.2.6. Telemetry now available
Copy link

With this release, MicroShift adds the Telemeter API. Lightweight attributes can be sent from a connected node to Red Hat to monitor the health of the node. To opt-out of Telemetry, see Remote health monitoring with a connected node.

1.3. Notable technical changes
Copy link

Learn about technical changes that include enhancements or changes in your workflow.

With this release, the MicroShift RPM includes the MicroShift multiple networking plug-in. To deploy the Multus container network interface (CNI), you can either set the value in the MicroShift configuration file, or install the microshift-multus RPM, which contains a configuration snippet. For more information, see About using multiple networks.

1.4. Technology Preview features
Copy link

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

1.4.1. Red Hat OpenShift AI with MicroShift
Copy link

With this release, a streamlined version of Red Hat OpenShift AI (RHOAI) can be used to serve artificial intelligence or machine learning (AI/ML) models on MicroShift. Develop and train your AI models in the data center or cloud, then deploy them to the edge where these models can make decisions without a human user. For more information, see Using Red Hat OpenShift AI with MicroShift.

1.5. Deprecated and removed features
Copy link

Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in and continues to be supported, but will be removed in a future release. Deprecated features and functionality are not recommended for new deployments.

The following functions related to checking workload health in the /usr/share/microshift/functions/greenboot.sh script are deprecated:

  • wait_for
  • namespace_images_downloaded
  • namespace_deployment_ready
  • namespace_daemonset_ready
  • namespace_pods_ready
  • namespace_pods_not_restarting
  • print_failure_logs
  • log_failure_cmd
  • log_script_exit
  • lvmsDriverShouldExist
  • csiComponentShouldBeDeploy

1.6. Bug fixes
Copy link

This release includes many fixes for bugs.

  • Before this update, using microshift-gitops in a disconnected environment failed because its manifests had the imagePullPolicy set to Always. In these cases, GitOps tried to pull images over a non-existent network and failed with an ImagePullBackoff error. With this update, the imagePullPolicy is set to IfNotPresent, which means that GitOps uses a local image and can start normally. (OCPBUGS-37938)
  • Previously, specific cipher suites required by MicroShift etcd when using TLS 1.2 were not included in the MicroShift startup configuration file. As a result, MicroShift failed to start when using TLS 1.2. With this release, the required cipher suites are in the configuration file by default and MicroShift can start normally when using TLS 1.2. (OCPBUGS-48735)
  • Previously, a .nodename file that holds the last hostname was created by MicroShift on startup non-atomically. When MicroShift’s startup was interrupted, the .nodename file was left behind empty. This .nodename file was used on the next MicroShift startup, causing the node name to stored as an empty string. This caused the API Server to reject the kubelet’s calls and the start up failed. With this release, the .nodename file is created atomically with each MicroShift start up, preventing the error. (OCPBUGS-48163)
  • By default, the MicroShift Logical Volume Manager Storage (LVMS) image copied the manifest list for four platforms because of automatic digest preservation. This action caused unnecessary usage of disk and network space. With this release, the manifest list is replaced with images specific to each architecture. Now, the MicroShift LVMS images only contain supported platform images, saving on disk space and network bandwidth. (OCPBUGS-51329)
  • Previously, the kustomizer sub-service was blocking microshift.service readiness by adding a manifest that required a webhook for a Custom Resource (CR) before MicroShift had started. This resulted kustomizer failing, causing MicroShift to fail. With this release, MicroShift is no longer dependent on the kustomizer sub-service, and can start even if a manifest is malformed by kustomizer. (OCPBUGS-51365)
  • In previous versions of MicroShift and RHEL, the MicroShift container-image-embedding procedure used the default container storage directory, which prevented proper image updates. With this release, the recommended image-embedding procedure was changed to use a dedicated directory for each image and a systemd service copying those embedded images into the default container storage. As a result, updates for image mode for RHEL are applied as expected with MicroShift and embedded containers. (OCPBUGS-52420)

1.7. Known issues
Copy link

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

  • The maximum transmission unit (MTU) value in MicroShift OVN-K overlay networking must be 100 bytes smaller than the MTU value of the base network. MicroShift automatically configures the value using the MTU value of the default gateway of the host. If the auto-configuration does not work correctly, the MTU value must be configured manually. For more information, see Network topology.

1.8. Additional release notes
Copy link

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

Note

The following release notes are for downstream Red Hat products only; upstream or community release notes for related products are not included.

1.8.1. GitOps release notes
Copy link

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 Red Hat package download page and search for "gitops" if you just need the latest package, Red Hat packages.

1.8.2. OpenShift Container Platform release notes
Copy link

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 9.6 for more information about RHEL.

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

1.9. Asynchronous errata updates
Copy link

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

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

Note

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

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

Issued: 17 June 2025

Red Hat build of MicroShift release 4.19.0 is now available. Bug fixes and enhancements are listed in the RHEA-2024:11040 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 RHSA-2024:11038 advisory.

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

Issued: 11 August 2025

Red Hat build of MicroShift release 4.19.7 is now available. Bug fixes and enhancements are listed in the RHBA-2025:12745 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 RHSA-2025:12341 advisory.

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

1.9.2.1. Bug fixes
Copy link

  • Before this update, a bare-metal node reboot caused the deployment progress deadline to be surpassed. This resulted in the greenboot health check failing with a false-positive error. With this release, the full timeout duration is provided for the deployment to become ready, reducing false-positive greenboot health check errors. (OCPBUGS-59301)
  • Before this update, the excessive polling frequency for the cloud pull secret in node telemetry caused telemetry failure messages to flood journald logs. The log flooding negatively impacted system performance. With this release, the telemetry collection interval is updated from 1 second to 30 seconds. As a result, log flooding has been minimized and no longer impacts system performance. (OCPBUGS-59240)

Issued: 04 March 2026

Red Hat build of MicroShift release 4.19.25 is now available. Bug fixes and enhancements are listed in the RHBA-2026:3508 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:3394 advisory.

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

1.9.3.1. Fixed issues
Copy link

There are no notable fixed issues for this release.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

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

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

Theme

© 2026 Red HatBack to top