Merge pull request #40294 from ousleyp/maximums-kcs

BZ1997540: replacing virt object maximum doc with KBase link

Author: ousleyp

modules/virt-about-cluster-limits.adoc

@@ -0,0 +1,16 @@
+// Module included in the following assemblies:
+//
+// * virt/install/virt-planning-environment-object-maximums.adoc
+
+[id="virt-about-cluster-limits_{context}"]
+
+= About cluster limits for {VirtProductName}
+
+To view the supported cluster limits for guests, hosts, and other objects, refer to link:https://access.redhat.com/articles/6571671[Supported Limits for {VirtProductName} 4.x].
+
+Red Hat has tested these values to ensure optimal cluster and workload performance. Exceeding the documented limits might result in unexpected behavior and degraded performance.
+
+[NOTE]
+====
+Guidelines for object maximums are based on the largest possible cluster. For smaller clusters, the maximums are lower.
+====

modules/virt-tested-cluster-maximums.adoc

@@ -5,11 +5,9 @@ include::modules/virt-document-attributes.adoc[]
 
 toc::[]
 
-You can plan your {VirtProductName} {VirtVersion} cluster by considering tested object maximums. Guidelines for object maximums are based on the largest possible cluster. For smaller clusters, the maximums are lower. In most cases, exceeding these numbers results in lower overall performance. It does not necessarily mean that the cluster will fail.
+Plan your cluster for {VirtProductName} by using tested object maximums as guidelines.
 
-The maximum number of virtual machines in a node is determined by a number of variables that include the virtual machines' CPUs, memory, and network characteristics.
-
-include::modules/virt-tested-cluster-maximums.adoc[leveloffset=+1]
+include::modules/virt-about-cluster-limits.adoc[leveloffset=+1]
 
 [id="additional-resources_{context}"]
 == Additional resources