Merge pull request #76255 from sr1kar99/9222-agent-installer-with-multiarch-payload

OSDOCS#9222: Agent installer with multi-arch payload

Author: stevsmit

installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc

@@ -25,12 +25,16 @@ The following procedures deploy a single-node {product-title} in a disconnected
 // Downloading the Agent-based Installer
 include::modules/installing-ocp-agent-download.adoc[leveloffset=+2]
 
+//Verifying architectures 
+include::modules/agent-installer-architectures.adoc[leveloffset=+2]
+
 // Creating the preferred configuration inputs
 include::modules/installing-ocp-agent-inputs.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 * xref:../../installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-customizations.adoc#configuring-vsphere-regions-zones_installing-vsphere-installer-provisioned-customizations[Configuring regions and zones for a VMware vCenter]
+* xref:../../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc#agent-install-verifying-architectures_installing-with-agent-based-installer[Verifying the supported architecture for installing an Agent-based installer cluster]
 
 [id="installing-ocp-agent-opt-manifests_{context}"]
 === Optional: Creating additional manifest files
@@ -88,6 +92,5 @@ include::modules/sample-ztp-custom-resources.adoc[leveloffset=+1]
 
 * See xref:../../edge_computing/ztp-deploying-far-edge-clusters-at-scale.adoc#ztp-deploying-far-edge-clusters-at-scale[Challenges of the network far edge] to learn more about {ztp-first}.
 
-
 // Gathering log data from a failed Agent-based installation
 include::modules/installing-ocp-agent-gather-log.adoc[leveloffset=+1]

modules/agent-installer-architectures.adoc

@@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * installing/installing-with-agent-based-installer/preparing-to-install-with-agent-based-installer.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="agent-install-verifying-architectures_{context}"]
+= Verifying the supported architecture for installing an Agent-based Installer cluster
+
+Before installing an {product-title} cluster using the Agent-based Installer, you can verify the supported architecture on which you can install the cluster. This procedure is optional.
+
+.Prerequisites: 
+
+* You installed the {oc-first}.
+* You have downloaded the installation program.
+
+.Procedure: 
+
+. Log in to the {oc-first}.
+
+. Check your release payload by running the following command: 
+[source,terminal]
++
+----
+$ ./openshift-install version
+----
++
+.Example output 
+[source,terminal]
+----
+./openshift-install 4.16.0
+built from commit abc123def456
+release image quay.io/openshift-release-dev/ocp-release@sha256:123abc456def789ghi012jkl345mno678pqr901stu234vwx567yz0
+release architecture amd64
+----
++
+If you are using the release image with the `multi` payload, the `release architecture` displayed in the output of this command is the default architecture.
+
+. To check the architecture of the payload, run the following command:
+[source,terminal]
++
+----
+$ oc adm release info <release_image> -o jsonpath="{ .metadata.metadata}" <1>
+----
+<1> Replace `<release_image>` with the release image. For example: `quay.io/openshift-release-dev/ocp-release@sha256:123abc456def789ghi012jkl345mno678pqr901stu234vwx567yz0`.
++
+.Example output when the release image uses the `multi` payload:
+[source,terminal]
+----
+{"release.openshift.io architecture":"multi"}
+----
++
+If you are using the release image with the `multi` payload, you can install the cluster on different architectures such as `arm64`, `amd64`, `s390x`, and `ppc64le`. Otherwise, you can install the cluster only on the `release architecture` displayed in the output of the `openshift-install version` command.

modules/installing-ocp-agent-inputs.adoc

@@ -77,7 +77,9 @@ pullSecret: '<pull_secret>' // <5>
 sshKey: '<ssh_pub_key>' // <6>
 EOF
 ----
-<1> Specify the system architecture, valid values are `amd64`, `arm64`, `ppc64le`, and `s390x`.
+<1> Specify the system architecture. Valid values are `amd64`, `arm64`, `ppc64le`, and `s390x`. 
++
+If you are using the release image with the `multi` payload, you can install the cluster on different architectures such as `arm64`, `amd64`, `s390x`, and `ppc64le`. Otherwise, you can install the cluster only on the `release architecture` displayed in the output of the `openshift-install version` command. For more information, see "Verifying the supported architecture for installing an Agent-based Installer cluster".
 <2> Required. Specify your cluster name.
 <3> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <4> Specify your platform.