diff --git a/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.adoc b/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.adoc
index 0324938a81ae..ecfc89030ba1 100644
--- a/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.adoc
+++ b/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn-past.adoc
@@ -10,6 +10,20 @@ 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-2151-6_{context}"]
+== Custom Metrics Autoscaler Operator 2.15.1-6 release notes
+
+Issued: 17 April 2025
+
+This release of the Custom Metrics Autoscaler Operator 2.15.1-6 addresses Common Vulnerabilities and Exposures (CVEs). The following advisory is available for the Custom Metrics Autoscaler Operator: 
+
+* link:https://access.redhat.com/errata/RHSA-2025:3993[RHSA-2025:3993]
+
+[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-2151-4_{context}"]
 == Custom Metrics Autoscaler Operator 2.15.1-4 release notes
 
diff --git a/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc b/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
index abf6d9ca8a71..6b2b5c1eb89b 100644
--- a/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
+++ b/nodes/cma/nodes-cma-rn/nodes-cma-autoscaling-custom-rn.adoc
@@ -26,46 +26,64 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
 |{product-title} version
 |General availability
 
-|2.15.1
+|2.17.2
 |4.18
 |General availability
 
-
-|2.15.1
+|2.17.2
 |4.17
 |General availability
 
-|2.15.1
+|2.17.2
 |4.16
 |General availability
 
-|2.15.1
+|2.17.2
 |4.15
 |General availability
 
-|2.15.1
+|2.17.2
 |4.14
 |General availability
 
-|2.15.1
+|2.17.2
 |4.13
 |General availability
 
-|2.15.1
+|2.17.2
 |4.12
 |General availability
 |===
 
-[id="nodes-pods-autoscaling-custom-rn-2151-6_{context}"]
-== Custom Metrics Autoscaler Operator 2.15.1-6 release notes
+[id="nodes-pods-autoscaling-custom-rn-2172_{context}"]
+== Custom Metrics Autoscaler Operator 2.17.2 release notes
 
 Issued: 17 April 2025
 
-This release of the Custom Metrics Autoscaler Operator 2.15.1-6 addresses Common Vulnerabilities and Exposures (CVEs). The following advisory is available for the Custom Metrics Autoscaler Operator: 
+This release of the Custom Metrics Autoscaler Operator 2.17.2 addresses Common Vulnerabilities and Exposures (CVEs), a new feature, and bug fixes. The following advisory is available for the Custom Metrics Autoscaler Operator: 
 
-* link:https://access.redhat.com/errata/RHSA-2025:3993[RHSA-2025:3993]
+* link:https://access.redhat.com/errata/RHSA-2025:TBD[RHSA-2025: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-2172-new-features_{context}"]
+=== New features and enhancements
+
+[id="nodes-pods-autoscaling-custom-rn-2172-new-features-controller_{context}"]
+==== The Keda Controller is now created upon installation of the Custom Metrics Autoscaler Operator
+
+With this update, when you install the Custom Metrics Autoscaler Operator, the installation program automatically creates the `KedaController` custom resource (CR), which creates several required custom resource definitions. Previously, you needed to manually create the `KedaController` CR. After installation, you can modify the KedaController` CR as needed, to change logging settings, the namespaces where the Custom Metrics Autoscaler operates, and other configurations. For more information, see 
+
+[id="nodes-pods-autoscaling-custom-rn-2172-new-features-token_{context}"]
+==== Bound service account token support
+
+With this update, you can now use bound service account tokens with trigger authentications and cluster trigger authentications. Bound service account tokens are audience- and time-bound, making them more secure than legacy service account tokens. 
+
+[id="nodes-pods-autoscaling-custom-rn-2172-bugs_{context}"]
+=== Bug fixes
+
+* Before this update, you were unable mount a volume to a Custom Metrics Autoscaler pod, because the Keda Controller did not support the `volumeMount` and `volume` parameters. With this update, the Keda Controller now supports these fields and you can inject volumes into Custom Metrics Autoscaler pods, if needed. (link:https://issues.redhat.com/browse/OCPBUGS-42559[*OCPBUGS-42559*])
+