BZ2024348: Add bare metal to the requirements for installing on a single node

BZ2024348: Edits based on feedback

BZ2025588: Fix the procedure for obtaining hub cluster deployment CRs

BZ2025588: Edits based on feedback

BZ2025588: PR edits based on feedback

Author: ogradyp

modules/install-sno-requirements-for-installing-on-a-single-node.adoc

@@ -9,6 +9,8 @@ Installing {product-title} on a single node alleviates some of the requirements
 
 * *Administration host:* You must have a computer to prepare the ISO, to create the USB boot drive, and to monitor the installation.
 
+* *Bare metal installation:* Installing {product-title} on a single node on bare metal requires that you specify the `platform.none: {}` parameter in the `install-config.yaml` configuration file.
+
 * *Production-grade server:* Installing {product-title} on a single node requires a server with sufficient resources to run {product-title} services and a production workload.
 +
 .Minimum resource requirements
@@ -20,7 +22,7 @@ Installing {product-title} on a single node alleviates some of the requirements
 +
 [NOTE]
 ====
-One vCPU is equivalent to one physical core when simultaneous multithreading (SMT), or hyperthreading, is not enabled. When enabled, use the following formula to calculate the corresponding ratio: 
+One vCPU is equivalent to one physical core when simultaneous multithreading (SMT), or hyperthreading, is not enabled. When enabled, use the following formula to calculate the corresponding ratio:
 
 (threads per core × cores) × sockets = vCPUs
 ====

modules/ztp-preparing-the-hub-cluster-for-ztp.adoc

@@ -19,7 +19,15 @@ $ oc get secret openshift-gitops-cluster -n openshift-gitops -o jsonpath='{.data
 ----
 
 . Prepare the ArgoCD pipeline configuration:
-.. Clone the Git repository.
+.. Extract the ArgoCD deployment CRs from the ZTP site generator container using the latest container image version:
++
+[source,terminal]
+----
+$ mkdir ztp
+$ podman run --rm -v `pwd`/ztp:/mnt/ztp:Z registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4.9.0-1 /bin/bash -c "cp -ar /usr/src/hook/ztp/* /mnt/ztp/"
+----
++
+The remaining steps in this section relate to the `ztp/gitops-subscriptions/argocd/` directory.
 
 .. Modify the source values of the two ArgoCD applications, `deployment/clusters-app.yaml` and `deployment/policies-app.yaml` with appropriate URL, `targetRevision` branch, and path values. The path values must match those used in your Git repository.
 +
@@ -53,7 +61,7 @@ spec:
        syncOptions:
        - CreateNamespace=true
 ----
-<1> `path` is the branch that contains the `siteconfig` CRs for the clusters.
+<1> `path` is the `ztp/gitops-subscriptions/argocd/` file path that contains the `siteconfig` CRs for the clusters.
 <2> `repoURL` is the URL of the Git repository that contains the `siteconfig` custom resources that define site configuration for installing clusters.
 <3> `targetRevision` is the branch on the Git repository that contains the relevant site configuration data.
 
@@ -89,13 +97,13 @@ spec:
        syncOptions:
        - CreateNamespace=true
 ----
-<1> `path` is the branch that contains the `policygentemplates` CRs for the clusters.
+<1> `path` is the `ztp/gitops-subscriptions/argocd/` file path that contains the `policygentemplates` CRs for the clusters.
 <2> `repoURL` is the URL of the Git repository that contains the `policygentemplates` custom resources that specify configuration data for the site.
 <3> `targetRevision` is the branch on the Git repository that contains the relevant configuration data.
 
 . To apply the pipeline configuration to your hub cluster, enter this command:
 +
 [source,terminal]
 ----
-oc apply -k ./deployment
+$ oc apply -k ./deployment
 ----