You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microshift_getting_started/microshift-architecture.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,38 +11,38 @@ Learn the specifics of {product-title} architecture including design intent, how
11
11
12
12
[id="microshift-architectural-design_{context}"]
13
13
== Architectural design
14
-
{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.
14
+
{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 {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.
15
15
16
-
For example, {product-title} contains only the following Kubernetes cluster capabilities:
16
+
For example, {microshift-short} contains only the following Kubernetes cluster capabilities:
17
17
18
18
* Networking
19
19
* Ingress
20
20
* Storage
21
21
* Helm
22
22
23
-
{product-title} also provides the following Kubernetes functions:
23
+
{microshift-short} also provides the following Kubernetes functions:
24
24
25
25
* Orchestration
26
26
* Security
27
27
28
-
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.
28
+
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.
29
29
30
30
.{product-title} as part of {op-system-bundle}.
31
31
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.>]
32
32
33
-
The following operational differences from {oke} can help you understand where {product-title} can be deployed:
33
+
The following operational differences from {oke} can help you understand where {microshift-short} can be deployed:
34
34
35
35
[id="microshift-differences-oke_{context}"]
36
36
== Key differences from {oke}
37
37
38
-
* Devices with {product-title} installed are self-managing
38
+
* Devices with {microshift-short} installed are self-managing
39
39
* Compatible with RPM-OStree-based systems
40
40
* Uses only the APIs needed for essential functions, such as security and runtime controls
41
41
* Enables a subset of commands from the OpenShift CLI (`oc`) tool
42
42
* Does not support workload high availability (HA) or horizontal scalability with the addition of worker nodes
43
43
44
44
.{product-title} differences from {oke}.
45
-
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.>]
45
+
image::311_RHDevice_Edge_Overview_0223_2.png[<{microshift-short} 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.>]
46
46
47
47
Figure 2 shows that {oke} has the same cluster capabilities as {product-title}, and adds the following:
Copy file name to clipboardExpand all lines: modules/microshift-about.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,12 @@
5
5
[id="con-about-microshift_{context}"]
6
6
= About {product-title}
7
7
8
-
Working with resource-constrained field environments and hardware presents many challenges not experienced with cloud computing. {product-title} enables you to solve problems for edge devices by:
8
+
Working with resource-constrained field environments and hardware presents many challenges not experienced with cloud computing. {microshift-short} enables you to solve problems for edge devices by:
9
9
10
10
* Running the same Kubernetes workloads you run in the cloud, but at the edge.
11
11
* Overcoming the operational challenge of minimal system resources.
12
12
* Addressing the environmental challenges of severe networking constraints such as low or no connectivity.
13
13
* Meeting the physical constraint of hard-to-access locations by installing your system images directly on edge devices.
14
14
* Building on and integrating with edge-optimized operating systems such as {op-system-ostree-first}.
15
15
16
-
{product-title} has the simplicity of single-node deployment with the functions and services you need for computing in resource-constrained locations. You can have many deployments on different hosts, creating the specific system image needed for each of your applications.
16
+
{microshift-short} has the simplicity of single-node deployment with the functions and services you need for computing in resource-constrained locations. You can have many deployments on different hosts, creating the specific system image needed for each of your applications.
0 commit comments