Merge pull request #46468 from abrennan89/HA-1829

[SRVCOM-1829] Update structure and abstracts for HA docs

Author: abrennan89

_topic_maps/_topic_map.yml

@@ -3479,7 +3479,7 @@ Topics:
   - Name: Serverless administrator metrics
     File: serverless-admin-metrics
     # HA
-  - Name: High availability on OpenShift Serverless
+  - Name: High availability
     File: serverless-ha
 - Name: Monitor
   Dir: monitor

_topic_maps/_topic_map_osd.yml

@@ -290,7 +290,7 @@ Topics:
     File: serverless-ossm-setup
   - Name: Serverless administrator metrics
     File: serverless-admin-metrics
-  - Name: High availability on OpenShift Serverless
+  - Name: High availability
     File: serverless-ha
 - Name: Monitor
   Dir: monitor

modules/serverless-config-replicas-eventing.adoc

@@ -6,7 +6,12 @@
 [id="serverless-config-replicas-eventing_{context}"]
 = Configuring high availability replicas for Knative Eventing
 
-You can scale Knative Eventing components by modifying the `spec.high-availability.replicas` value in the `KnativeEventing` custom resource (CR).
+High availability (HA) is available by default for the Knative Eventing `eventing-controller`, `eventing-webhook`, `imc-controller`, `imc-dispatcher`, `mt-broker-controller`, and `sugar-controller` components, which are configured to have two replicas each by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeEventing` custom resource (CR).
+
+[NOTE]
+====
+For Knative Eventing, the `mt-broker-filter` and `mt-broker-ingress` deployments are not scaled by HA. If multiple deployments are needed, scale these components manually.
+====
 
 .Prerequisites
 
@@ -44,10 +49,5 @@ metadata:
   namespace: knative-eventing
 spec:
   high-availability:
-    replicas: 3 <1>
+    replicas: 3
 ----
-<1> Sets the number of replicas to `3`.
-+
-* The `replicas` value sets the replica count for all HA controllers.
-* The default `replicas` value is `2`.
-* You can increase the number of replicas by changing the value to `3` or more.

modules/serverless-config-replicas-kafka.adoc

@@ -6,7 +6,7 @@
 [id="serverless-config-replicas-kafka_{context}"]
 = Configuring high availability replicas for Knative Kafka
 
-You can scale Knative Kafka components by modifying the `spec.high-availability.replicas` value in the `KnativeKafka` custom resource (CR).
+High availability (HA) is available by default for the Knative Kafka `kafka-controller` and `kafka-webhook-eventing` components, which are configured to have two each replicas by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeKafka` custom resource (CR).
 
 .Prerequisites
 
@@ -44,10 +44,5 @@ metadata:
   namespace: knative-eventing
 spec:
   high-availability:
-    replicas: 3 <1>
+    replicas: 3
 ----
-<1> Sets the number of replicas to `3`.
-+
-* The `replicas` value sets the replica count for all HA controllers.
-* The default `replicas` value is `2`.
-* You can increase the number of replicas by changing the value to `3` or more.

modules/serverless-config-replicas-serving.adoc

@@ -6,7 +6,7 @@
 [id="serverless-config-replicas-serving_{context}"]
 = Configuring high availability replicas for Knative Serving
 
-You can scale Knative Serving components by modifying the `spec.high-availability.replicas` value in the `KnativeServing` custom resource (CR).
+High availability (HA) is available by default for the Knative Serving `activator`, `autoscaler`, `autoscaler-hpa`, `controller`, `webhook`, `kourier-control`, and `kourier-gateway` components, which are configured to have two replicas each by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeServing` custom resource (CR).
 
 .Prerequisites
 
@@ -44,10 +44,5 @@ metadata:
   namespace: knative-serving
 spec:
   high-availability:
-    replicas: 3 <1>
+    replicas: 3
 ----
-<1> Sets the number of replicas to `3`.
-+
-* The `replicas` value sets the replica count for all HA controllers.
-* The default `replicas` value is `2`.
-* You can increase the number of replicas by changing the value to `3` or more.

serverless/admin_guide/serverless-ha.adoc

@@ -1,7 +1,7 @@
 :_content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="serverless-ha"]
-= High availability on {ServerlessProductName}
+= High availability
 :context: serverless-ha
 
 toc::[]
@@ -11,21 +11,6 @@ High availability (HA) is a standard feature of Kubernetes APIs that helps to en
 HA in {ServerlessProductName} is available through leader election, which is enabled by default after the Knative Serving or Eventing control plane is installed. When using a leader election HA pattern, instances of controllers are already scheduled and running inside the cluster before they are required.
 These controller instances compete to use a shared resource, known as the leader election lock. The instance of the controller that has access to the leader election lock resource at any given time is called the leader.
 
-[id="serverless-ha-configuring-replicas"]
-== Configuring high availability replicas on {ServerlessProductName}
-
-High availability (HA) functionality is available by default on {ServerlessProductName} for Knative Serving, Knative Eventing, and Knative Kafka. These are the components scaled for each of them:
-
-* Knative Serving: `activator`, `autoscaler`, `autoscaler-hpa`, `controller`, `webhook`, `kourier-control`, `kourier-gateway`.
-* Knative Eventing: `eventing-controller`, `eventing-webhook`, `imc-controller`, `imc-dispatcher`, `mt-broker-controller`, `sugar-controller`.
-* Knative Kafka: `kafka-ch-controller`, `kafka-controller-manager`, `kafka-webhook`.
-
-These components are configured with two replicas by default.
-
-For Knative Eventing, the `mt-broker-filter` and `mt-broker-ingress` deployments are not scaled by HA. If multiple deployments are needed, scale these components manually.
-
-You modify the number of replicas that are created per component by changing the configuration of `spec.high-availability.replicas` in the KnativeServing custom resource (CR), the KnativeEventing CR, or the KnativeKafka CR.
-
 include::modules/serverless-config-replicas-serving.adoc[leveloffset=+2]
 include::modules/serverless-config-replicas-eventing.adoc[leveloffset=+2]
 include::modules/serverless-config-replicas-kafka.adoc[leveloffset=+2]