Merge pull request #61137 from mburke5678/cma-replace-kafka-tp

CMA adding the Kafka TP note back

Author: mburke5678

modules/nodes-cma-autoscaling-custom-install.adoc

@@ -15,11 +15,11 @@ ifdef::openshift-origin[]
 If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in _Configuring {product-title} to use Red Hat Operators_.
 endif::openshift-origin[]
 
-* If you use the community KEDA:
+* Remove any previously-installed Technology Preview versions of the Cluster Metrics Autoscaler Operator.
 
-** Uninstall the community KEDA. You cannot run both KEDA and the custom metrics autoscaler on the same {product-title} cluster.
-
-** Remove the KEDA 1.x custom resource definitions by running the following commands:
+* Remove any versions of the community-based KEDA.
++
+Also, remove the KEDA 1.x custom resource definitions by running the following commands:
 +
 [source,terminal]
 ----

modules/nodes-cma-autoscaling-custom-pausing-restart.adoc

@@ -40,7 +40,7 @@ metadata:
   generation: 1
   name: scaledobject
   namespace: my-project
-  resourceVersion: "65729"
+  resourceVersion: '65729'
   uid: f5aec682-acdf-4232-a783-58b5b82f5dd0
 ----
 <1> Remove this annotation to restart a paused custom metrics autoscaler.

modules/nodes-cma-autoscaling-custom-pausing-workload.adoc

@@ -40,7 +40,7 @@ metadata:
   generation: 1
   name: scaledobject
   namespace: my-project
-  resourceVersion: "65729"
+  resourceVersion: '65729'
   uid: f5aec682-acdf-4232-a783-58b5b82f5dd0
 ----
 <1> Specifies that the Custom Metrics Autoscaler Operator is to scale the replicas to the specified value and stop autoscaling.

modules/nodes-cma-autoscaling-custom-trigger-kafka.adoc

@@ -8,6 +8,9 @@
 
 You can scale pods based on an Apache Kafka topic or other services that support the Kafka protocol. The custom metrics autoscaler does not scale higher than the number of Kafka partitions, unless you set the `allowIdleConsumers` parameter to `true` in the scaled object or scaled job.
 
+:FeatureName: Autoscaling based on Apache Kafka metrics
+include::snippets/technology-preview.adoc[leveloffset=+0]
+
 [NOTE]
 ====
 If the number of consumer groups exceeds the number of partitions in a topic, the extra consumer groups remain idle. To avoid this, by default the number of replicas does not exceed:

nodes/cma/nodes-cma-autoscaling-custom-rn.adoc

@@ -52,6 +52,11 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
 
 This release of the Custom Metrics Autoscaler Operator 2.10.1 provides new features and bug fixes for running the Operator in an {product-title} cluster. The components of the Custom Metrics Autoscaler Operator 2.10.1 were released in link:https://access.redhat.com/errata/RHEA-2023:3199[RHEA-2023:3199].
 
+[IMPORTANT]
+====
+Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously-installed Technology Preview versions or the community-supported version of KEDA.
+====
+
 [id="nodes-pods-autoscaling-custom-rn-210-new_{context}"]
 === New features and enhancements
 
@@ -63,6 +68,9 @@ The Custom Metrics Autoscaler Operator is now generally available as of Custom M
 :FeatureName: Scaling by using a scaled job
 include::snippets/technology-preview.adoc[]
 
+:FeatureName: Autoscaling based on Apache Kafka metrics
+include::snippets/technology-preview.adoc[leveloffset=+0]
+
 [id="nodes-pods-autoscaling-custom-rn-210-metrics_{context}"]
 ==== Performance metrics
 

nodes/cma/snippets

@@ -0,0 +1 @@
+../../snippets/