mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
77 lines
3.7 KiB
Plaintext
77 lines
3.7 KiB
Plaintext
:_content-type: ASSEMBLY
|
|
[id="microshift-architecture"]
|
|
= Architecture
|
|
include::_attributes/attributes-microshift.adoc[]
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: microshift-architecture
|
|
|
|
toc::[]
|
|
|
|
Learn the specifics of {product-title} architecture including design intent, how it differs from {oke}, and API compatibility.
|
|
|
|
[id="microshift-architectural-design_{context}"]
|
|
== Architectural design
|
|
{product-title} is a single-node container orchestration runtime designed to extend the benefits of using containers for running applications to low-resource edge environments. Because {product-title} 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, {product-title} contains only the following Kubernetes cluster capabilities:
|
|
|
|
* Networking
|
|
* Ingress
|
|
* Storage
|
|
* Helm
|
|
|
|
{product-title} also provides the following Kubernetes functions:
|
|
|
|
* Orchestration
|
|
* Security
|
|
|
|
To optimize your deployments, use {product-title} with a compatible operating system, such as {op-system-ostree-first}. Using {product-title} and {op-system-ostree-first} together forms {op-system-bundle}. Virtual machines are handled by the operating system in {product-title} 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 cluster 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 {product-title} can be deployed:
|
|
|
|
[id="microshift-differences-oke_{context}"]
|
|
== Key differences from {oke}
|
|
|
|
* Devices with {product-title} 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
|
|
|
|
.{product-title} differences from {oke}.
|
|
image::311_RHDevice_Edge_Overview_0223_2.png[<{product-title} is tasked with only the Kubernetes cluster capabilities of networking, ingress, storage, helm, with the additional Kubernetes functions of orchestration and security, as the following diagram illustrates.>]
|
|
|
|
Figure 2 shows that {oke} has the same cluster capabilities as {product-title}, and adds the following:
|
|
|
|
* Install
|
|
* Over-the-air updates
|
|
* Cluster 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 {product-title}, functions such as over-the-air-updates, monitoring, and logging, are performed by the operating system.
|
|
|
|
[id="microshift-openshift-apis_{context}"]
|
|
== {product-title} OpenShift APIs
|
|
|
|
In addition to standard Kubernetes APIs, {product-title} includes a small subset of the APIs supported by {OCP}.
|
|
|
|
[cols="1,1",options="header"]
|
|
|===
|
|
^| API ^| API group
|
|
| xref:../microshift_rest_api/network_apis/route-route-openshift-io-v1.adoc#route-route-openshift-io-v1[Route]
|
|
| route.openshift.io/v1
|
|
| xref:../microshift_rest_api/security_apis/securitycontextconstraints-security-openshift-io-v1.adoc#securitycontextconstraints-security-openshift-io-v1[SecurityContextConstraints]
|
|
| security.openshift.io/v1
|
|
|===
|
|
|
|
include::modules/microshift-k8s-apis.adoc[leveloffset=+1] |