- Home
- Local Kubernetes Tools
- MicroShift
MicroShift
What it is
MicroShift is an OpenShift/Kubernetes project tailored to small systems and edge deployments, where compute, storage, and network capacity may be constrained. It aims to use CPU, memory, network, and storage sparingly and to tolerate difficult network conditions. Updates are designed to be delivered securely and quickly without interrupting workloads. MicroShift runs as one systemd service, combining a minimal OpenShift control plane and worker node. Included infrastructure services are DNS, an ingress router, service CA, OVN-Kubernetes CNI, and LVMS storage; optional OLM, Gateway API, cert-manager, and SR-IOV components are available as separate RPM packages. It uses CRI-O and supports a local registry and add-on catalog, but not multi-node clusters or a graphical interface. Stated minimums include x86_64 or aarch64, Red Hat Enterprise Linux with Extended Update Support, 2 CPU cores, 2GB RAM, and 2GB free root storage. The upstream development and testing build is free at no cost and does not require Red Hat subscriptions or pull secrets. Production deployments can use bare metal or hypervisors certified for Red Hat Enterprise Linux 9.
For and against
For
- Runs as a single systemd service.
- Includes DNS, ingress, service CA, OVN-Kubernetes, and LVMS.
- Optional components are available as separate RPM packages.
- Upstream development and testing build is free.
- Supports x86_64 and aarch64 architectures.
Against
- Requires Red Hat Enterprise Linux with Extended Update Support.
- Minimums include 2 CPU cores, 2GB RAM, and 2GB storage.
- Does not support multi-node clusters.
- Has no graphical interface.
The verdict
MicroShift packages a minimal OpenShift control plane and worker node for edge and small-form deployments. Check the stated operating system and hardware requirements, and note that it is designed for single-node use.
Who it suits
MicroShift suits teams deploying a compact OpenShift/Kubernetes environment on edge hardware or other resource-constrained systems. The upstream build is also intended for contributors and testers.
Plans and prices
MicroShift Upstream
Upstream development and testing build; no Red Hat subscriptions or pull secrets required
Read 8 Oct 2026 · github.com
On the record
- Architecture
- MicroShift runs as a single systemd service with a minimal OpenShift control plane and worker node.github.com · read 7 Oct 2026
- Architectures
- MicroShift and its main components are available for x86_64 and aarch64 architectures.github.com · read 8 Oct 2026
- Deployment
- MicroShift can run on the host or inside a Bootc container.github.com · read 8 Oct 2026
- Distribution
- RPM and DEB packages built in a container can be installed and run on the listed operating systems.github.com · read 8 Oct 2026
- Documentation
- The upstream repository links documentation for building, versioning, host deployment, Bootc deployment, and GitHub workflows.github.com · read 8 Oct 2026
- Downloads
- Prebuilt MicroShift artifacts are published on the repository's Releases page, and nightly RPMs are published on COPR.github.com · read 8 Oct 2026
- Included services
- The listed infrastructure services include DNS, ingress router, service CA, OVN-Kubernetes CNI, and LVMS storage.github.com · read 7 Oct 2026
- License
- The repository lists an Apache-2.0 license.github.com · read 7 Oct 2026
- Networking
- Its design goals include tolerating severe networking constraints.github.com · read 7 Oct 2026
- Operating systems
- The upstream repository lists CentOS 9, CentOS 10, Fedora, Ubuntu, and macOS deployment options, with macOS using Podman machine in rootful mode.github.com · read 8 Oct 2026
- Optional components
- Optional components listed include OLM, Gateway API, cert-manager, and SR-IOV, delivered as separate RPM packages.github.com · read 7 Oct 2026
- Production use
- The openshift/microshift repository says production deployments can run on bare metal hardware or hypervisors supported and certified for Red Hat Enterprise Linux 9.github.com · read 8 Oct 2026
- Purpose
- MicroShift optimizes OpenShift Kubernetes for small form factor and edge computing.github.com · read 8 Oct 2026
- Requirements
- The stated minimums include x86_64 or aarch64 CPU architecture, Red Hat Enterprise Linux with Extended Update Support, 2 CPU cores, 2GB RAM, and 2GB free root storage.github.com · read 7 Oct 2026
- Resource use
- Its design goals include frugal use of CPU, memory, network, and storage resources.github.com · read 7 Oct 2026
- Scope
- The openshift/microshift repository describes MicroShift as a small form factor OpenShift/Kubernetes project optimized for edge computing.github.com · read 8 Oct 2026
- Subscription distinction
- The upstream repository says its build runs without Red Hat subscriptions or pull secrets.github.com · read 8 Oct 2026
- Updates
- Its design goals include updating securely, safely, speedily, and seamlessly without disrupting workloads.github.com · read 7 Oct 2026
