OSDOCS-12013 specified z-stream version to scale to 250 nodes in HCP

Author: xJustin

modules/rosa-sdpolicy-instance-types.adoc

@@ -14,6 +14,12 @@ endif::[]
 
 ifdef::rosa-with-hcp[]
 All {hcp-title} clusters require a minimum of 2 worker nodes. All {hcp-title} clusters support a maximum of 250 worker nodes. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss.
+
+[NOTE]
+====
+Customers running {hcp-title} 4.14.x and 4.15.x clusters require a minimum z-stream version of 4.14.28 or 4.15.15 and greater to scale to 250 worker nodes. For earlier versions, the maximum is 90 worker nodes. 
+====
+
 endif::rosa-with-hcp[]
 ifndef::rosa-with-hcp[]
 Single availability zone clusters require a minimum of 3 control plane nodes, 2 infrastructure nodes, and 2 worker nodes deployed to a single availability zone.

modules/sd-hcp-planning-cluster-maximums.adoc

@@ -10,6 +10,10 @@ Consider the following tested object maximums when you plan a {hcp-title-first}
 
 These guidelines are based on a cluster of 250 compute (also known as worker) nodes. For smaller clusters, the maximums are lower.
 
+[NOTE]
+====
+Customers running {hcp-title} 4.14.x and 4.15.x clusters require a minimum z-stream version of 4.14.28 or 4.15.15 and greater to scale to 250 worker nodes. For earlier versions, the maximum is 90 worker nodes. 
+====
 
 .Tested cluster maximums
 [options="header",cols="50,50"]

rosa_architecture/rosa_policy_service_definition/rosa-hcp-instance-types.adoc

@@ -9,7 +9,7 @@ toc::[]
 
 [NOTE]
 ====
-Currently, {hcp-title} supports a maximum of 250 worker nodes.
+Currently, {hcp-title} supports a maximum of 250 worker nodes. Customers running {hcp-title} 4.14.x and 4.15.x clusters require a minimum z-stream version of 4.14.28 or 4.15.15 and greater to scale to 250 worker nodes. For earlier versions, the maximum is 90 worker nodes. 
 ====
 
 include::modules/rosa-sdpolicy-am-aws-compute-types.adoc[leveloffset=+1]