Merge pull request #58246 from mburke5678/cma-release-nodes-282-174

CMA 2.8.2-174 release notes

Author: mburke5678

modules/nodes-pods-autoscaling-custom-gather.adoc

@@ -32,7 +32,7 @@ $ oc adm must-gather --image="$(oc get packagemanifests openshift-custom-metrics
 
 [NOTE]
 ====
-The standard {product-title} must-gather command, `oc adm must-gather`, does not collect Custom Metrics Autoscaler Operator data.
+The standard {product-title} `must-gather` command, `oc adm must-gather`, does not collect Custom Metrics Autoscaler Operator data.
 ====
 
 

modules/nodes-pods-autoscaling-custom-rn.adoc

@@ -26,23 +26,42 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
 |{product-title} version
 |General availability
 
-|2.8.2
-|4.13
-|Technology Preview
-
-|2.8.2
+|2.8.2-174
 |4.12
 |Technology Preview
 
-|2.8.2
+|2.8.2-174
 |4.11
 |Technology Preview
 
-|2.8.2
+|2.8.2-174
 |4.10
 |Technology Preview
 |===
 
+[id="nodes-pods-autoscaling-custom-rn-282-174_{context}"]
+== Custom Metrics Autoscaler Operator 2.8.2-174 release notes
+
+This release of the Custom Metrics Autoscaler Operator 2.8.2-174 provides new features and bug fixes for running the Operator in an {product-title} cluster. The components of the Custom Metrics Autoscaler Operator 2.8.2-174 were released in link:https://access.redhat.com/errata/RHEA-2023:1683[RHEA-2023:1683].
+
+[IMPORTANT]
+====
+The Custom Metrics Autoscaler Operator is currently a link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview] feature.
+====
+
+[id="nodes-pods-autoscaling-custom-rn-282-174-new_{context}"]
+=== New features and enhancements
+
+[id="autoscaling-custom-2-8-2-upgrade-operator"]
+==== Operator upgrade support
+
+You can now upgrade from a prior version of the Custom Metrics Autoscaler Operator. See "Changing the update channel for an Operator" in the "Additional resources" for information on upgrading an Operator.
+
+[id="autoscaling-custom-2-8-2-must-gather"]
+==== must-gather support
+
+You can now collect data about the Custom Metrics Autoscaler Operator and its components by using the {product-title} `must-gather` tool. Currently, the process for using the `must-gather` tool with the Custom Metrics Autoscaler is different than for other operators. See "Gathering debugging data in the "Additional resources" for more information.
+
 [id="nodes-pods-autoscaling-custom-rn-282_{context}"]
 == Custom Metrics Autoscaler Operator 2.8.2 release notes
 
@@ -54,24 +73,31 @@ The Custom Metrics Autoscaler Operator is currently a link:https://access.redhat
 ====
 
 [id="nodes-pods-autoscaling-custom-rn-282-new_{context}"]
-New features and enhancements
+=== New features and enhancements
 
 [id="autoscaling-custom-2-8-2-audit-log"]
-=== Audit Logging
+==== Audit Logging
 
 You can now gather and view audit logs for the Custom Metrics Autoscaler Operator and its associated components. Audit logs are security-relevant chronological sets of records that document the sequence of activities that have affected the system by individual users, administrators, or other components of the system.  
 
 [id="autoscaling-custom-2-8-2-kafka-metrics"]
-=== Scale applications based on Apache Kafka metrics
+==== Scale applications based on Apache Kafka metrics
 
 You can now use the KEDA Apache kafka trigger/scaler to scale deployments based on an Apache Kafka topic.
 
+[IMPORTANT]
+====
+Autoscaling based on Apache Kafka metrics is a Technology Preview (TP) feature in all Custom Metrics Autoscaler TP releases and the Custom Metrics Autoscaler General Availability release.
+ 
+Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. 
+====
+
 [id="autoscaling-custom-2-8-2-cpu-metrics"]
-=== Scale applications based on CPU metrics
+==== Scale applications based on CPU metrics
 
 You can now use the KEDA CPU trigger/scaler to scale deployments based on CPU metrics.
 
 [id="autoscaling-custom-2-8-2-memory-metrics"]
-=== Scale applications based on memory metrics
+==== Scale applications based on memory metrics
 
 You can now use the KEDA memory trigger/scaler to scale deployments based on memory metrics.

nodes/pods/nodes-pods-autoscaling-custom.adoc

@@ -29,6 +29,8 @@ include::modules/nodes-pods-autoscaling-custom-rn.adoc[leveloffset=+1]
 
 .Additional resources
 
+* xref:../../operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing the update channel for an Operator]
+* xref:../../nodes/pods/nodes-pods-autoscaling-custom.html#nodes-pods-autoscaling-custom-gather_nodes-pods-autoscaling-custom[Gathering debugging data]
 * xref:../../nodes/pods/nodes-pods-autoscaling-custom.adoc#nodes-pods-autoscaling-custom-audit_nodes-pods-autoscaling-custom[Configuring audit logging]
 * xref:../../nodes/pods/nodes-pods-autoscaling-custom.adoc#nodes-pods-autoscaling-custom-trigger-cpu_nodes-pods-autoscaling-custom[Understanding the CPU trigger]
 * xref:../../nodes/pods/nodes-pods-autoscaling-custom.adoc#nodes-pods-autoscaling-custom-trigger-memory_nodes-pods-autoscaling-custom[Understanding the memory trigger]