Microshift is OpenShift¹ Kubernetes in a small form factor and optimized for edge computing.

Edge devices deployed out in the field pose very different operational, environmental, and business challenges from those of cloud computing. These motivate different engineering trade-offs for Kubernetes at the far edge than for cloud or near-edge scenarios. Microshift's design goals cater to this:

• make frugal use of system resources (CPU, memory, network, storage, etc.),
• tolerate severe networking constraints,
• update (resp. roll back) securely, safely, speedily, and seamlessly (without disrupting workloads), and
• build on and integrate cleanly with edge-optimized OSes like Fedora IoT and RHEL for Edge, while
• providing a consistent development and management experience with standard OpenShift.

We believe these properties should also make Microshift a great tool for other use cases such as Kubernetes applications development on resource-constrained systems, scale testing, and provisioning of lightweight Kubernetes control planes.

Note: Microshift is still early days and moving fast. Features are missing. Things break. But you can still help shape it, too.

^{1) more precisely OKD, the Kubernetes distribution by the OpenShift community}

To give Microshift a try, simply install a recent test version (we don't provide stable releases yet) on a Fedora-derived Linux distro (we've only tested Fedora, RHEL, and CentOS Stream so far) using:

curl -sfL https://raw.githubusercontent.com/redhat-et/microshift/main/install.sh | sh -

This will install Microshift's dependencies (CRI-O), install it as a systemd service and start it.

For convenience, the script will also add a new "microshift" context to your $HOME/.kube/config, so you'll be able to access your cluster using, e.g.:

kubectl get all -A --context microshift

or

kubectl config use-context microshift
kubectl get all -A

Notes: When installing Microshift on a system with an older version already installed, it is safest to remove the old data directory and start fresh:

rm -rf /var/lib/microshift && rm -r $HOME/.microshift

You can locally build Microshift using one of two methods, either using a container build (recommended) on Podman or Docker:

make microshift

or directly on the host after installing the build-time dependencies

sudo dnf install -y glibc-static
make

Use install.sh to set up your sytem and install run-time dependencies for Microshift, then simply:

sudo microshift run

Microshift keeps all its state in its data-dir, which defaults to /var/lib/microshift when running Microshift as privileged user and $HOME/.microshift otherwise. Note that running Microshift unprivileged only works without node role at the moment (i.e. using --roles=controlplane instead of the default of --roles=controlplane,node).

You can find the kubeadmin's kubeconfig under $DATADIR/resources/kubeadmin/kubeconfig.