|
| 1 | +:_mod-docs-content-type: ASSEMBLY |
| 2 | +[id="ibi-understanding-image-based-install"] |
| 3 | += Understanding image-based installation and deployment for {sno} |
| 4 | +include::_attributes/common-attributes.adoc[] |
| 5 | +:context: ibi-understanding-image-based-install |
| 6 | + |
| 7 | +toc::[] |
| 8 | + |
| 9 | +Image-based installations significantly reduce the deployment time of {sno} clusters by streamlining the installation process. |
| 10 | + |
| 11 | +This approach enables the preinstallation of configured and validated instances of {sno} on target hosts. These preinstalled hosts can be rapidly reconfigured and deployed at the far edge of the network, including in disconnected environments, with minimal intervention. |
| 12 | + |
| 13 | +[NOTE] |
| 14 | +==== |
| 15 | +To deploy a managed cluster using an imaged-based approach in combination with {ztp-first}, you can use the SiteConfig operator. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html-single/multicluster_engine_operator_with_red_hat_advanced_cluster_management/index#siteconfig-intro[SiteConfig operator]. |
| 16 | +==== |
| 17 | + |
| 18 | +[id="ibi-installation-deployment-overview_{context}"] |
| 19 | +== Overview of image-based installation and deployment for {sno} clusters |
| 20 | + |
| 21 | +Deploying infrastructure at the far edge of the network presents challenges for service providers with low bandwidth, high latency, and disconnected environments. |
| 22 | +It is also costly and time-consuming to install and deploy {sno} clusters. |
| 23 | + |
| 24 | +An image-based approach to installing and deploying {sno} clusters at the far edge of the network overcomes these challenges by separating the installation and deployment stages. |
| 25 | + |
| 26 | +.Overview of an image-based installation and deployment for managed {sno} clusters |
| 27 | +image::../images/711_OpenShift_IBI_Installation_high-level_0624.png[Overview of an image-based installation and deployment] |
| 28 | + |
| 29 | +Imaged-based installation:: |
| 30 | +Preinstall multiple hosts with {sno} at a central site, such as a service depot or a factory. |
| 31 | +Then, validate the base configuration for these hosts and leverage the image-based approach to perform reproducible factory installs at scale by using a single live installation ISO. |
| 32 | + |
| 33 | +Image-based deployment:: |
| 34 | +Ship the preinstalled and validated hosts to a remote site and rapidly reconfigure and deploy the clusters in a matter of minutes by using a configuration ISO. |
| 35 | + |
| 36 | +You can choose from two methods to preinstall and configure your SNO clusters. |
| 37 | + |
| 38 | +Using the `openshift-install` program:: |
| 39 | +For a {sno} cluster, use the `openshift-install` program only to manually create the live installation ISO that is common to all hosts. Then, use the program again to create the configuration ISO which ensures that the host is unique. For more information, see “Deploying managed {sno} using the openshift-install program”. |
| 40 | + |
| 41 | +Using the IBI Operator:: |
| 42 | +For managed {sno} clusters, you can use the `openshift-install` with the Image Based Install (IBI) Operator to scale up the operations. The program creates the live installation ISO and then the IBI Operator creates one configuration ISO for each host. For more information, see “Deploying {sno} using the IBI Operator”. |
| 43 | + |
| 44 | +[id="ibi-installation-overview_{context}"] |
| 45 | +=== Image-based installation for {sno} clusters |
| 46 | + |
| 47 | +Using the {lcao}, you can generate an OCI container image that encapsulates an instance of a {sno} cluster. This image is derived from a dedicated cluster that you can configure with the target {product-title} version. |
| 48 | + |
| 49 | +You can reference this image in a live installation ISO to consistently preinstall configured and validated instances of {sno} to multiple hosts. This approach enables the preparation of hosts at a central location, for example in a factory or service depot, before shipping the preinstalled hosts to a remote site for rapid reconfiguration and deployment. The instructions for preinstalling a host are the same whether you deploy the host by using only the `openshift-install` program or using the program with the IBI Operator. |
| 50 | + |
| 51 | +The following is a high-level overview of the image-based installation process: |
| 52 | + |
| 53 | +. Generate an image from a {sno} cluster. |
| 54 | +. Use the `openshift-install` program to embed the seed image URL, and other installation artifacts, in a live installation ISO. |
| 55 | +. Start the host using the live installation ISO to preinstall the host. |
| 56 | ++ |
| 57 | +During this process, the `openshift-install` program installs {op-system-first} to the disk, pulls the image you generated, and precaches release container images to the disk. |
| 58 | + |
| 59 | +. When the installation completes, the host is ready to ship to the remote site for rapid reconfiguration and deployment. |
| 60 | + |
| 61 | +[id="ibi-deployment-overview_{context}"] |
| 62 | +=== Image-based deployment for {sno} clusters |
| 63 | + |
| 64 | +You can use the `openshift-install` program or the IBI Operator to configure and deploy a host that you preinstalled with an image-based installation. |
| 65 | + |
| 66 | +{sno-caps} cluster deployment:: |
| 67 | + |
| 68 | +To configure the target host with site-specific details by using the `openshift-install` program, you must create the following resources: |
| 69 | ++ |
| 70 | +-- |
| 71 | +* The `install-config.yaml` installation manifest |
| 72 | + |
| 73 | +* The `image-based-config.yaml` manifest |
| 74 | +-- |
| 75 | ++ |
| 76 | +The `openshift-install` program uses these resources to generate a configuration ISO that you attach to the preinstalled target host to complete the deployment. |
| 77 | + |
| 78 | +Managed {sno} cluster deployment:: |
| 79 | + |
| 80 | +{rh-rhacm-first} and the {mce} (MCE) use a hub-and-spoke architecture to manage and deploy {sno} clusters across multiple sites. Using this approach, the hub cluster serves as a central control plane that manages the spoke clusters, which are often remote {sno} clusters deployed at the far edge of the network. |
| 81 | ++ |
| 82 | +You can define the site-specific configuration resources for an image-based deployment in the hub cluster. The IBI Operator uses these configuration resources to reconfigure the preinstalled host at the remote site and deploy the host as a managed {sno} cluster. This approach is especially beneficial for telecommunications providers and other service providers with extensive, distributed infrastructures, where an end-to-end installation at the remote site would be time-consuming and costly. |
| 83 | ++ |
| 84 | +The following is a high-level overview of the image-based deployment process for hosts preinstalled with an imaged-based installation: |
| 85 | ++ |
| 86 | +-- |
| 87 | +* Define the site-specific configuration resources for the preinstalled host in the hub cluster. |
| 88 | +* Apply these resources in the hub cluster. This initiates the deployment process. |
| 89 | +* The IBI Operator creates a configuration ISO. |
| 90 | +* The IBI Operator boots the target preinstalled host with the configuration ISO attached. |
| 91 | +* The host mounts the configuration ISO and begins the reconfiguration process. |
| 92 | +* When the reconfiguration completes, the {sno} cluster is ready. |
| 93 | +-- |
| 94 | ++ |
| 95 | +As the host is already preinstalled using an image-based installation, a technician can reconfigure and deploy the host in a matter of minutes. |
| 96 | + |
| 97 | +[id="ibi-installation-deployment-components_{context}"] |
| 98 | +== Image-based installation and deployment components |
| 99 | + |
| 100 | +The following content describes the components in an image-based installation and deployment. |
| 101 | + |
| 102 | +Seed image:: OCI container image generated from a dedicated cluster with the target {product-title} version. |
| 103 | + |
| 104 | +Seed cluster:: Dedicated {sno} cluster that you use to create a seed image and is deployed with the target {product-title} version. |
| 105 | + |
| 106 | +{lcao}:: Generates the seed image. |
| 107 | + |
| 108 | +Image Based Install (IBI) Operator:: When you deploy managed clusters, the IBI Operator creates a configuration ISO from the site-specific resources you define in the hub cluster, and attaches the configuration ISO to the preinstalled host by using a bare-metal provisioning service. |
| 109 | + |
| 110 | +`openshift-install` program:: Creates the installation and configuration ISO, and embeds the seed image URL in the live installation ISO. If the IBI Operator is not used, you must manually attach the configuration ISO to a preinstalled host to complete the deployment. |
| 111 | + |
| 112 | +[role="_additional-resources"] |
| 113 | +.Additional resources |
| 114 | + |
| 115 | +* xref:../../edge_computing/image_base_install/ibi_deploying_sno_clusters/ibi-edge-image-based-install-standalone.adoc#create-standalone-config-iso_ibi-edge-image-based-install[Deploying a {sno} cluster using the `openshift-install` program] |
| 116 | + |
| 117 | +include::modules/ibi-image-based-install-cluster-guide.adoc[leveloffset=+1] |
| 118 | + |
| 119 | +[role="_additional-resources"] |
| 120 | +.Additional resources |
| 121 | + |
| 122 | +* xref:../../edge_computing/image_base_install/ibi-preparing-for-image-based-install.adoc#cnf-image-based-upgrade-shared-container-partition_ibi-preparing-image-based-install[Configuring a shared container partition between ostree stateroots] |
| 123 | + |
| 124 | +include::modules/ibi-validated-software-versions.adoc[leveloffset=+1] |
| 125 | + |
| 126 | +[role="_additional-resources"] |
| 127 | +.Additional resources |
| 128 | + |
| 129 | +* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/about/welcome-to-red-hat-advanced-cluster-management-for-kubernetes#multicluster-architecture[Multicluster architecture] |
| 130 | + |
| 131 | +* xref:../../edge_computing/image_based_upgrade/cnf-understanding-image-based-upgrade.adoc#cnf-understanding-image-based-upgrade[Understanding the image-based upgrade for {sno} clusters] |
0 commit comments