Key differences from OpenShift Kubernetes Engine

  • Devices with MicroShift installed are self-managing

  • Compatible with rpm-ostree-based systems

  • Uses only the APIs needed for essential functions, such as security and runtime controls

  • Enables a subset of commands from the OpenShift CLI (oc) tool

  • Does not support workload high availability (HA) or horizontal scalability with the addition of worker nodes

<MicroShift is tasked with only the Kubernetes node capabilities of networking
Figure 2. {product-title} differences from OpenShift Kubernetes Engine.

The figure "{product-title} differences from OpenShift Kubernetes Engine" shows that OpenShift Kubernetes Engine has the same cluster capabilities as a {product-title} node, and adds the following information:

  • Install

  • Over-the-air updates

  • Operators

  • Operator Lifecycle Manager

  • Monitoring

  • Logging

  • Registry

  • Authorization

  • Console

  • Cloud Integration

  • Virtual Machines (VMs) through OpenShift Virtualization

In OpenShift Kubernetes Engine and other OpenShift Container Platform deployments, all of the components from the operating system through the cluster capabilities work as one comprehensive unit, with full cluster services for a multi-node Kubernetes workload. With MicroShift, functions such as over-the-air-updates, monitoring, and logging, are performed by the operating system.

↑ Up: Architectural design | ⌂ Home: Red Hat build of MicroShift | Next: About this release →