openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

GH#36703 Diagram refers to RHCOS instead of FCOS

Browse Source
This commit is contained in:
Michael Burke
2021-11-11 11:16:58 -05:00
committed by openshift-cherrypick-robot
parent 19b786f172
commit 03ca0b32dc
6 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
images/150_OpenShift_VMware_on_AWS_1021_installer_FCOS.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 58 KiB

BIN
images/193_OpenShift_Cluster_Install_updates_1021_oVirt.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 84 KiB

5
installing/installing_rhv/installing-rhv-customizations.adoc
View File

@@ -7,7 +7,12 @@ toc::[]
You can customize and install an {product-title} cluster on {rh-virtualization-first}, similar to the one shown in the following diagram.
ifndef::openshift-origin[]
image::92_OpenShift_Cluster_Install_RHV_0520.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
ifdef::openshift-origin[]
image::193_OpenShift_Cluster_Install_updates_1021_oVirt.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
The installation program uses installer-provisioned infrastructure to automate creating and deploying the cluster.

5
installing/installing_rhv/installing-rhv-default.adoc
View File

@@ -7,7 +7,12 @@ toc::[]
You can quickly install a default, non-customized, {product-title} cluster on a {rh-virtualization-first} cluster, similar to the one shown in the following diagram.
ifndef::openshift-origin[]
image::92_OpenShift_Cluster_Install_RHV_0520.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
ifdef::openshift-origin[]
image::193_OpenShift_Cluster_Install_updates_1021_oVirt.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
The installation program uses installer-provisioned infrastructure to automate creating and deploying the cluster.

9
installing/installing_rhv/installing-rhv-user-infra.adoc
View File

@@ -10,7 +10,14 @@ customized {product-title} cluster on {rh-virtualization-first} and other infras
The following diagram shows an example of a potential {product-title} cluster running on a {rh-virtualization} cluster.
image::92_OpenShift_Cluster_Install_RHV_0520.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster. The {rh-virtualization} hosts run virtual machines that contain both control plane and compute pods. One of the hosts also runs a {rh-virtualization-engine-name} virtual machine and a bootstrap virtual machine that contains a temporary control plane pod.]
ifndef::openshift-origin[]
image::92_OpenShift_Cluster_Install_RHV_0520.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
ifdef::openshift-origin[]
image::193_OpenShift_Cluster_Install_updates_1021_oVirt.png[Diagram of an {product-title} cluster on a {rh-virtualization} cluster]
endif::openshift-origin[]
The {rh-virtualization} hosts run virtual machines that contain both control plane and compute pods. One of the hosts also runs a {rh-virtualization-engine-name} virtual machine and a bootstrap virtual machine that contains a temporary control plane pod.]
== Prerequisites

6
modules/installation-process.adoc
View File

@@ -70,8 +70,14 @@ If your cluster uses user-provisioned infrastructure, you have the option of add
Because each machine in the cluster requires information about the cluster when it is provisioned, {product-title} uses a temporary _bootstrap_ machine during initial configuration to provide the required information to the permanent control plane. It boots by using an Ignition config file that describes how to create the cluster. The bootstrap machine creates the control plane machines that make up the control plane. The control plane machines then create the compute machines, which are also known as worker machines. The following figure illustrates this process:
ifndef::openshift-origin[]
.Creating the bootstrap, control plane, and compute machines
image::create-nodes.png[Creating bootstrap, control plane, and compute machines]
endif::openshift-origin[]
ifdef::openshift-origin[]
.Creating the bootstrap, control plane, and compute machines
image::150_OpenShift_VMware_on_AWS_1021_installer_FCOS.png[Creating bootstrap, control plane, and compute machines]
endif::openshift-origin[]
After the cluster machines initialize, the bootstrap machine is destroyed. All clusters use the bootstrap process to initialize the cluster, but if you provision the infrastructure for your cluster, you must complete many of the steps manually.