Merge pull request #28429 from abrennan89/glossary01

[SRVCOM-967] Updating terms and clean up serverless docs sections

Author: bergerhoffer

modules/serverless-cluster-sizing-req.adoc

@@ -0,0 +1,24 @@
+// Module is included in the following assemblies:
+//
+// serverless/installing_serverless/installing-openshift-serverless.adoc
+
+[id="serverless-cluster-sizing-req_{context}"]
+= Defining cluster size requirements for an {ServerlessProductName} installation
+
+To install and use {ServerlessProductName}, the {product-title} cluster must be sized correctly.
+The minimum requirement for {ServerlessProductName} is a cluster with 10 CPUs and 40GB memory.
+The total size requirements to run {ServerlessProductName} are dependent on the applications deployed. By default, each pod requests approximately 400m of CPU, so the minimum requirements are based on this value.
+In the size requirement provided, an application can scale up to 10 replicas. Lowering the actual CPU request of applications can increase the number of possible replicas.
+
+[NOTE]
+====
+The requirements provided relate only to the pool of worker machines of the {product-title} cluster. Master nodes are not used for general scheduling and are omitted from the requirements.
+====
+
+[NOTE]
+====
+The following limitations apply to all {ServerlessProductName} deployments:
+
+* Maximum number of Knative services: 1000
+* Maximum number of Knative revisions: 1000
+====

serverless/installing_serverless/installing-openshift-serverless.adoc

@@ -13,46 +13,27 @@ This guide walks cluster administrators through installing the {ServerlessOperat
 {ServerlessProductName} is supported for installation in a restricted network environment. For more information, see xref:../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks].
 ====
 
-[id="installing-openshift-serverless-cluster-sizing"]
-== Cluster sizing requirements
-
-To run {ServerlessProductName}, the {product-title} cluster must be sized correctly.
-The minimum requirement to use {ServerlessProductName} is a cluster with 10 CPUs and 40GB memory.
-
-The total size requirements to run {ServerlessProductName} are dependent on the applications deployed. By default, each pod requests ~400m of CPU, so the minimum requirements are based on this value.
-
-In the size requirement provided, an application can scale up to 10 replicas. Lowering the actual CPU request of applications can increase the number of possible replicas.
-
-You can use the MachineSet API to manually scale your cluster up to the desired size. The minimum requirements usually mean that you must scale up one of the default MachineSets by two additional machines.
-
-For more information on using the MachineSet API, see the documentation on xref:../../machine_management/creating_machinesets/creating-machineset-aws.adoc#creating-machineset-aws[Creating MachineSets].
-
-For more information on scaling a MachineSet manually, see the documentation on xref:../../machine_management/manually-scaling-machineset.adoc#manually-scaling-machineset[manually scaling MachineSets].
-
-[NOTE]
-====
-The requirements provided relate only to the pool of worker machines of the {product-title} cluster. Master nodes are not used for general scheduling and are omitted from the requirements.
+[IMPORTANT]
 ====
-
-[NOTE]
+Before upgrading to the latest Serverless release, you must remove the community Knative Eventing Operator if you have previously installed it. Having the Knative Eventing Operator installed will prevent you from being able to install the latest version of Knative Eventing using the {ServerlessOperatorName}.
 ====
-The following limitations apply to all {ServerlessProductName} deployments:
 
-* Maximum number of Knative services: 1000
-* Maximum number of Knative revisions: 1000
-====
+include::modules/serverless-cluster-sizing-req.adoc[leveloffset=+1]
 
-=== Additional requirements for advanced use-cases
+[id="installing-openshift-serverless-advanced-reqs"]
+== Additional requirements for advanced use cases
 
-For more advanced use-cases such as logging or metering on {product-title}, you must deploy more resources. Recommended requirements for such use-cases are 24 CPUs and 96GB of memory.
+For more advanced use cases such as logging or metering on {product-title}, you must deploy more resources. Recommended requirements for such use cases are 24 CPUs and 96GB of memory.
 
 If you have high availability (HA) enabled on your cluster, this requires between 0.5 - 1.5 cores and between 200MB - 2GB of memory for each replica of the Knative Serving control plane.
 HA is enabled for some Knative Serving components by default. You can disable HA by following the documentation on xref:../../serverless/serverless-HA.adoc#serverless-HA[Configuring high availability replicas on {ServerlessProductName}].
 
-[IMPORTANT]
-====
-Before upgrading to the latest Serverless release, you must remove the community Knative Eventing Operator if you have previously installed it. Having the Knative Eventing Operator installed will prevent you from being able to install the latest version of Knative Eventing using the {ServerlessOperatorName}.
-====
+[id="installing-openshift-serverless-scaling-with-machinesets"]
+== Scaling your cluster using machine sets
+
+You can use the {product-title} `MachineSet` API to manually scale your cluster up to the desired size.
+The minimum requirements usually mean that you must scale up one of the default machine sets by two additional machines.
+See xref:../../machine_management/manually-scaling-machineset.adoc#manually-scaling-machineset[Manually scaling a machine set].
 
 include::modules/serverless-install-web-console.adoc[leveloffset=+1]