2.2. 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

图 2.2. Red Hat build of MicroShift differences from OpenShift Kubernetes Engine.

<MicroShift is tasked with only the Kubernetes cluster capabilities of networking

The figure "Red Hat build of MicroShift differences from OpenShift Kubernetes Engine" shows that OpenShift Kubernetes Engine has the same cluster capabilities as Red Hat build of MicroShift, and adds the following information:

  • Install
  • Over-the-air updates
  • Cluster 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.

Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

关于红帽文档

Legal Notice

Theme

© 2026 Red Hat
返回顶部