CMA 2.14.1.NEXT release notes

Author: Michael Burke

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

@@ -10,6 +10,21 @@ The following release notes are for previous versions of the Custom Metrics Auto
 
 For the current version, see xref:../../../nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc#nodes-cma-autoscaling-custom-rn[Custom Metrics Autoscaler Operator release notes].
 
+[id="nodes-pods-autoscaling-custom-rn-2141-467_{context}"]
+== Custom Metrics Autoscaler Operator 2.14.1-467 release notes
+
+This release of the Custom Metrics Autoscaler Operator 2.14.1-467 provides a CVE and a bug fix for running the Operator in an {product-title} cluster. The following advisory is available for the link:https://access.redhat.com/errata/RHSA-2024:7348[RHSA-2024:7348].
+
+[IMPORTANT]
+====
+Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of Kubernetes-based Event Driven Autoscaler (KEDA).
+====
+
+[id="nodes-pods-autoscaling-custom-rn-2141-467-bugs_{context}"]
+=== Bug fixes
+
+* Previously, the root file system of the Custom Metrics Autoscaler Operator pod was writable, which is unnecessary and could present security issues. This update makes the pod root file system read-only, which addresses the potential security issue. (link:https://issues.redhat.com/browse/OCPBUGS-37989[*OCPBUGS-37989*])
+
 [id="nodes-pods-autoscaling-custom-rn-2141_{context}"]
 == Custom Metrics Autoscaler Operator 2.14.1-454 release notes
 

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

@@ -47,17 +47,25 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
 |General availability
 |===
 
-[id="nodes-pods-autoscaling-custom-rn-2141-467_{context}"]
-== Custom Metrics Autoscaler Operator 2.14.1-467 release notes
+[id="nodes-pods-autoscaling-custom-rn-2141-TDB_{context}"]
+== Custom Metrics Autoscaler Operator 2.14.1-TBD release notes
 
-This release of the Custom Metrics Autoscaler Operator 2.14.1-467 provides a CVE and a bug fix for running the Operator in an {product-title} cluster. The following advisory is available for the link:https://access.redhat.com/errata/RHSA-2024:7348[RHSA-2024:7348].
+This release of the Custom Metrics Autoscaler Operator 2.14.1-TBD provides a CVE and a bug fix for running the Operator in an {product-title} cluster. The following advisory is available for the link:https://access.redhat.com/errata/RHSA-2024:TBD[RHSA-2024:TBD].
 
 [IMPORTANT]
 ====
 Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of Kubernetes-based Event Driven Autoscaler (KEDA).
 ====
 
-[id="nodes-pods-autoscaling-custom-rn-2141-467-bugs_{context}"]
-=== Bug fixes
-
-* Previously, the root file system of the Custom Metrics Autoscaler Operator pod was writable, which is unnecessary and could present security issues. This update makes the pod root file system read-only, which addresses the potential security issue. (link:https://issues.redhat.com/browse/OCPBUGS-37989[*OCPBUGS-37989*])
+[id="nodes-pods-autoscaling-custom-rn-2141-TBD-new-features_{context}"]
+=== New features and enhancements
+
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you had to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation or xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually enable monitoring] for the `opensift-keda` project after installation. This option is now enabled by default upon installation of the Operator. You can xref:../../../observability/monitoring/enabling-monitoring-for-user-defined-projects.adoc#disabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[manually disable monitoring] for the `opensift-keda` project, as needed. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-dedicated[]
+* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you had to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation. This option is now enabled by default upon installation of the Operator. You can xref:../../../observability/monitoring/sd-disabling-monitoring-for-user-defined-projects.adoc#sd-disabling-monitoring-for-user-defined-projects_sd-disabling-monitoring-for-user-defined-projects[manually disable monitoring] for the `opensift-keda` project, as needed. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
+endif::openshift-rosa,openshift-dedicated[]
+ifdef::openshift-rosa-hcp[]
+* Previously, if you wanted the Custom Metrics Autoscaler Operator to scrape metrics, alerts, and so forth from the `openshift-keda` namespace, you had to select the `Enable Operator recommended cluster monitoring on this Namespace` option upon installation. This option is now enabled by default upon installation of the Operator. (link:https://issues.redhat.com/browse/PODAUTO-242[*PODAUTO-2428*])
+endif::openshift-rosa-hcp[]