Merge pull request #90748 from lg-rh/ibmz-new-hcp418

[OCPBUGS-52834] IBM Z Changes for HCP418

Author: xenolinux

hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc

@@ -42,6 +42,12 @@ include::modules/hcp-ibm-z-infra-reqs.adoc[leveloffset=+1]
 
 include::modules/hcp-ibm-z-dns.adoc[leveloffset=+1]
 include::modules/hcp-bm-hc.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc#hcp-bm-hc-console_hcp-deploy-bm[Creating a hosted cluster on bare metal by using the console]
+
 include::modules/hcp-ibm-z-infraenv.adoc[leveloffset=+1]
 
 [id="hcp-ibm-z-add-agents"]

modules/destroy-hc-ibm-z-cli.adoc

@@ -6,7 +6,7 @@
 [id="destroy-hc-ibmz-cli_{context}"]
 = Destroying a hosted cluster on x86 bare metal with {ibm-z-title} compute nodes
 
-To destroy a hosted cluster and its managed cluster on `x86` bare metal with {ibm-z-title} compute nodes, you can use the command-line interface (CLI).
+To destroy a hosted cluster and its managed cluster on `x86` bare metal with {ibm-z-name} compute nodes, you can use the command-line interface (CLI).
 
 .Procedure
 
@@ -31,6 +31,7 @@ $ oc --kubeconfig <hosted_cluster_name>.kubeconfig delete \
   node <compute_node_name>
 ----
 ====
+If you are using an OSA network device in Processor Resource/Systems Manager (PR/SM) mode, auto scaling is not supported. You must delete the old agent manually and scale up the node pool because the new agent joins during the scale down process. 
 
 . Verify the status of the compute nodes by entering the following command:
 +

modules/hcp-bm-autoscale.adoc

@@ -104,10 +104,8 @@ $ oc --kubeconfig ./hostedcluster-secrets -n <namespace> \
 ----
 $ oc --kubeconfig ./hostedcluster-secrets get nodes
 ----
-
++
 [NOTE]
 ====
-For {ibm-z-title} agents, compute nodes are detached from the cluster only for {ibm-z-title} with KVM agents. For z/VM and LPAR, you must delete the compute nodes manually.
-
-Agents can be reused only for {ibm-z-title} with KVM. For z/VM and LPAR, re-create the agents to use them as compute nodes.
-====
+For {ibm-z-name} agents, if you are using an OSA network device in Processor Resource/Systems Manager (PR/SM) mode, auto scaling is not supported. You must delete the old agent manually and scale up the node pool because the new agent joins during the scale down process.
+====

modules/hcp-ibm-z-scale-np.adoc

@@ -10,8 +10,6 @@ The `NodePool` object is created when you create a hosted cluster. By scaling th
 
 When you scale up a node pool, a machine is created. The Cluster API provider finds an Agent that is approved, is passing validations, is not currently in use, and meets the requirements that are specified in the node pool specification. You can monitor the installation of an Agent by checking its status and conditions.
 
-When you scale down a node pool, Agents are unbound from the corresponding cluster. Before you reuse the clusters, you must boot the clusters by using the PXE image to update the number of nodes.
-
 .Procedure
 
 . Run the following command to scale the `NodePool` object to two nodes: