|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * nodes/pods/nodes-pods-user-namespaces.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: REFERENCE |
| 6 | +[id="nodes-pods-autoscaling-custom-rn-2172_{context}"] |
| 7 | += Custom Metrics Autoscaler Operator 2.17.2 release notes |
| 8 | + |
| 9 | +Issued: 25 September 2025 |
| 10 | + |
| 11 | +This release of the Custom Metrics Autoscaler Operator 2.17.2 addresses Common Vulnerabilities and Exposures (CVEs). The following advisory is available for the Custom Metrics Autoscaler Operator: |
| 12 | + |
| 13 | +* link:https://access.redhat.com/errata/RHSA-2025:16124[RHSA-2025:16124] |
| 14 | +
|
| 15 | +[IMPORTANT] |
| 16 | +==== |
| 17 | +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). |
| 18 | +==== |
| 19 | + |
| 20 | +[id="nodes-pods-autoscaling-custom-rn-2172-new_{context}"] |
| 21 | +== New features and enhancements |
| 22 | + |
| 23 | +[id="nodes-pods-autoscaling-custom-rn-2172-new-controller_{context}"] |
| 24 | +=== The KEDA controller is automatically created during installation |
| 25 | + |
| 26 | +The KEDA controller is now automatically created when you install the Custom Metrics Autoscaler Operator. Previously, you needed to manually create the KEDA controller. You can edit the automatically-created KEDA controller, as needed. |
| 27 | + |
| 28 | +[id="nodes-pods-autoscaling-custom-rn-2172-workload_{context}"] |
| 29 | +=== Support for the Kubernetes workload trigger |
| 30 | + |
| 31 | +The Cluster Metrics Autoscaler Operator now supports using the Kubernetes workload trigger to scale pods based on the number of pods matching a specific label selector. |
| 32 | + |
| 33 | +[id="nodes-pods-autoscaling-custom-rn-2172-new-tokens_{context}"] |
| 34 | +=== Support for bound service account tokens |
| 35 | + |
| 36 | +The Cluster Metrics Autoscaler Operator now supports bound service account tokens. Previously, the Operator supported only legacy service account tokens, which are being phased out in favor of bound service account tokens for security reasons. |
| 37 | + |
| 38 | +[id="nodes-pods-autoscaling-custom-rn-2172-bugs_{context}"] |
| 39 | +== Bug fixes |
| 40 | + |
| 41 | +* Previously, the KEDA controller did not support volume mounts. As a result, you could not use Kerberos with the Kafka scaler. With this fix, the KEDA controller now supports volume mounts. (link:https://issues.redhat.com/browse/OCPBUGS-42559[OCPBUGS-42559]) |
| 42 | +* Previously, the KEDA version in the `keda-operator` deployment object log reported that the Custom Metrics Autoscaler Operator was based on an incorrect KEDA version. With this fix, the correct KEDA version is reported in the log. (link:https://issues.redhat.com/browse/OCPBUGS-58129[OCPBUGS-58129]) |
0 commit comments