mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
56 lines
2.9 KiB
Plaintext
56 lines
2.9 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// microshift/understanding-microshift.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-architectural-design_{context}"]
|
|
== Architectural design
|
|
|
|
{microshift-short} is a single-node container orchestration runtime designed to extend the benefits of using containers for running applications to low-resource edge environments. Because {microshift-short} is primarily a platform for deploying applications, only the APIs and features essential to operating in edge and small form factor computing environments are included.
|
|
|
|
For example, {microshift-short} has only the following Kubernetes node capabilities:
|
|
|
|
* Networking
|
|
* Ingress
|
|
* Storage
|
|
|
|
{microshift-short} also provides the following Kubernetes functions:
|
|
|
|
* Orchestration
|
|
* Security
|
|
|
|
To optimize your deployments, use {microshift-short} with a compatible operating system, such as {op-system-ostree-first}. Using {microshift-short} and {op-system-ostree-first} together forms {op-system-bundle}. Virtual machines are handled by the operating system in {microshift-short} deployments.
|
|
|
|
.{product-title} as part of {op-system-bundle}.
|
|
image::311_RHDevice_Edge_Overview_0223_1.png[<{product-title} is tasked with only the Kubernetes node services networking, ingress, storage, helm, with additional Kubernetes functions of orchestration and security, as the following diagram illustrates.>]
|
|
|
|
The following operational differences from {oke} can help you understand where you can deploy {microshift-short}:
|
|
|
|
[id="microshift-differences-oke_{context}"]
|
|
== Key differences from {oke}
|
|
|
|
* Devices with {microshift-short} 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 {oc-first} tool
|
|
* Does not support workload high availability (HA) or horizontal scalability with the addition of worker nodes
|
|
|
|
.{product-title} differences from {oke}.
|
|
image::311_RHDevice_Edge_Overview_0223_2.png[<{microshift-short} is tasked with only the Kubernetes node capabilities of networking, ingress, storage, helm, with the additional Kubernetes functions of orchestration and security, as the following diagram illustrates.>]
|
|
|
|
The figure "{product-title} differences from {oke}" shows that {oke} 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 {VirtProductName}
|
|
|
|
In {oke} and other {OCP} 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-short}, functions such as over-the-air-updates, monitoring, and logging, are performed by the operating system.
|