final tidy up for GitOps ZTP SNO worker nodes

Author: aireilly

_topic_maps/_topic_map.yml

@@ -2547,7 +2547,7 @@ Topics:
       File: ztp-talm-updating-managed-policies
     - Name: Updating GitOps ZTP
       File: ztp-updating-gitops
-    - Name: Adding worker nodes to single-node OpenShift cluster
+    - Name: Expanding single-node OpenShift clusters with GitOps ZTP
       File: ztp-sno-additional-worker-node
     - Name: Pre-caching images for single-node OpenShift deployments
       File: ztp-precaching-tool

modules/ztp-additional-worker-to-sno-cluster.adoc

@@ -1,12 +1,25 @@
 :_content-type: ASSEMBLY
 [id="ztp-sno-additional-worker-node"]
-= Adding worker nodes to {sno} clusters with GitOps ZTP
+= Expanding {sno} clusters with GitOps ZTP
 include::_attributes/common-attributes.adoc[]
 :context: sno-additional-worker
 
 toc::[]
 
-You can add one or more worker nodes to an existing {sno} cluster with GitOps ZTP. Adding worker nodes does not require any downtime for the existing {sno}.
+You can expand {sno} clusters with GitOps ZTP. When you add worker nodes to {sno} clusters, the original {sno} cluster retains the control plane node role. Adding worker nodes does not require any downtime for the existing {sno} cluster.
+
+[NOTE]
+====
+Although there is no specified limit on the number of worker nodes that you can add to a {sno} cluster, you must revaluate the reserved CPU allocation on the control plane node for the additional worker nodes.
+====
+
+If you require workload partitioning on the worker node, you must deploy and remediate the managed cluster policies on the hub cluster before installing the node. This way, the workload partitioning `MachineConfig` objects are rendered and associated with the `worker` machine config pool before the GitOps ZTP workflow applies the `MachineConfig` ignition file to the worker node.
+
+It is recommended that you first remediate the policies, and then install the worker node.
+If you create the workload partitioning manifests after installing the worker node, you must drain the node manually and delete all the pods managed by daemon sets. When the managing daemon sets create the new pods, the new pods undergo the workload partitioning process.
+
+:FeatureName: Adding worker nodes to {sno} clusters with GitOps ZTP
+include::snippets/technology-preview.adoc[]
 
 [role="_additional-resources"]
 .Additional resources
@@ -15,14 +28,12 @@ You can add one or more worker nodes to an existing {sno} cluster with GitOps ZT
 
 * For more information about worker nodes, see xref:../../nodes/nodes/nodes-sno-worker-nodes.adoc[Adding worker nodes to single-node OpenShift clusters].
 
-include::modules/ztp-additional-worker-to-sno-cluster.adoc[leveloffset=+1]
-
-include::modules/ztp-worker-node-applying-du-profile.adoc[leveloffset=+2]
+include::modules/ztp-worker-node-applying-du-profile.adoc[leveloffset=+1]
 
-include::modules/ztp-worker-node-daemon-selector-compatibility.adoc[leveloffset=+2]
+include::modules/ztp-worker-node-daemon-selector-compatibility.adoc[leveloffset=+1]
 
-include::modules/ztp-worker-node-node-selector-compatibility.adoc[leveloffset=+2]
+include::modules/ztp-worker-node-node-selector-compatibility.adoc[leveloffset=+1]
 
-include::modules/ztp-worker-node-preparing-policies.adoc[leveloffset=+2]
+include::modules/ztp-worker-node-preparing-policies.adoc[leveloffset=+1]
 
-include::modules/ztp-adding-worker-nodes.adoc[leveloffset=+2]
+include::modules/ztp-adding-worker-nodes.adoc[leveloffset=+1]