CMA 2.11.1 release notes

Author: Michael Burke

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

@@ -30,23 +30,48 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
 |{product-title} version
 |General availability
 
-|2.10.1-267
+|2.11.2
 |4.13
 |General availability
 
-|2.10.1-267
+|2.11.2
 |4.12
 |General availability
 
-|2.10.1-267
+|2.11.2
 |4.11
 |General availability
 
-|2.10.1-267
+|2.11.2
 |4.10
 |General availability
 |===
 
+[id="nodes-pods-autoscaling-custom-rn-2112_{context}"]
+== Custom Metrics Autoscaler Operator 2.11.2-311 release notes
+
+This release of the Custom Metrics Autoscaler Operator 2.11.2-311 provides new features and bug fixes for running the Operator in an {product-title} cluster. The components of the Custom Metrics Autoscaler Operator 2.11.2-311 were released in link:https://access.redhat.com/errata/RHBA-2023:5981[RHBA-2023:5981].
+
+[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-2112-new_{context}"]
+=== New features and enhancements
+
+[id="nodes-pods-autoscaling-custom-rn-2112-new-rosa-osd_{context}"]
+==== Red Hat OpenShift Service on AWS (ROSA) and OpenShift Dedicated are now supported 
+
+The Custom Metrics Autoscaler Operator 2.11.2-311 can be installed on OpenShift ROSA and OpenShift Dedicated managed clusters. Previous versions of the Custom Metrics Autoscaler Operator could be installed only in the `openshift-keda` namespace. This prevented the Operator from being installed on OpenShift ROSA and OpenShift Dedicated clusters. This version of Custom Metrics Autoscaler allows installation to other namespaces such as `openshift-operators` or `keda`, enabling installation into ROSA and Dedicated clusters. 
+
+[id="nodes-pods-autoscaling-custom-rn-2112-bugs_{context}"]
+=== Bug fixes
+
+* Previously, if the Custom Metrics Autoscaler Operator was installed and configured, but not in use, the OpenShift CLI reported the `couldn't get resource list for external.metrics.k8s.io/v1beta1: Got empty response for: external.metrics.k8s.io/v1beta1` error after any `oc` command was entered. The message, although harmless, could have caused confusion. With this fix, the `Got empty response for: external.metrics...` error no longer appears inappropriately. (link:https://issues.redhat.com/browse/OCPBUGS-15779[*OCPBUGS-15779*])
+
+* Previously, any annotation or label change to objects managed by the Custom Metrics Autoscaler were reverted by Custom Metrics Autoscaler Operator any time the Keda Controller was modified, for example after a configuration change. This caused continuous changing of labels in your objects. The Custom Metrics Autoscaler now uses its own annotation to manage labels and annotations, and annotation or label are no longer inappropriately reverted. (link:https://issues.redhat.com/browse/OCPBUGS-15590[*OCPBUGS-15590*])
+
 [id="nodes-pods-autoscaling-custom-rn-210-267_{context}"]
 == Custom Metrics Autoscaler Operator 2.10.1-267 release notes