Skip to content

Commit 61cc51e

Browse files
authored
Merge pull request #74864 from mburke5678/cma-2.12.1-384-rn
CMA 2.12.1-384 RN
2 parents 9d963e2 + 9ce3a8d commit 61cc51e

File tree

2 files changed

+22
-7
lines changed

2 files changed

+22
-7
lines changed

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

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,23 @@ The following release notes are for previous versions of the Custom Metrics Auto
1010

1111
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].
1212

13+
[id="nodes-pods-autoscaling-custom-rn-2121-376_{context}"]
14+
== Custom Metrics Autoscaler Operator 2.12.1-376 release notes
15+
16+
This release of the Custom Metrics Autoscaler Operator 2.12.1-376 provides security updates and bug fixes for running the Operator in an {product-title} cluster. The following advisory is available for the link:https://access.redhat.com/errata/RHSA-2024:1812[RHSA-2024:1812].
17+
18+
[IMPORTANT]
19+
====
20+
Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of KEDA.
21+
====
22+
23+
[id="nodes-pods-autoscaling-custom-rn-2121-376-bugs_{context}"]
24+
=== Bug fixes
25+
26+
* Previously, if invalid values such as nonexistent namespaces were specified in scaled object metadata, the underlying scaler clients would not free, or close, their client descriptors, resulting in a slow memory leak. This fix properly closes the underlying client descriptors when there are errors, preventing memory from leaking. (link:https://issues.redhat.com/browse/OCPBUGS-30145[*OCPBUGS-30145*])
27+
28+
* Previously the `ServiceMonitor` custom resource (CR) for the `keda-metrics-apiserver` pod was not functioning, because the CR referenced an incorrect metrics port name of `http`. This fix corrects the `ServiceMonitor` CR to reference the proper port name of `metrics`. As a result, the Service Monitor functions properly. (link:https://issues.redhat.com/browse/OCPBUGS-25806[*OCPBUGS-25806*])
29+
1330
[id="nodes-pods-autoscaling-custom-rn-2112-322_{context}"]
1431
== Custom Metrics Autoscaler Operator 2.11.2-322 release notes
1532

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

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -43,19 +43,17 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
4343
|General availability
4444
|===
4545

46-
[id="nodes-pods-autoscaling-custom-rn-2121-376_{context}"]
47-
== Custom Metrics Autoscaler Operator 2.12.1-376 release notes
46+
[id="nodes-pods-autoscaling-custom-rn-2121-384_{context}"]
47+
== Custom Metrics Autoscaler Operator 2.12.1-384 release notes
4848

49-
This release of the Custom Metrics Autoscaler Operator 2.12.1-376 provides security updates and bug fixes for running the Operator in an {product-title} cluster. The following advisory is available for the link:https://access.redhat.com/errata/RHSA-2024:1812[RHSA-2024:1812].
49+
This release of the Custom Metrics Autoscaler Operator 2.12.1-384 provides 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-TDB[RHSA-TDB].
5050

5151
[IMPORTANT]
5252
====
5353
Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of KEDA.
5454
====
5555

56-
[id="nodes-pods-autoscaling-custom-rn-2121-376-bugs_{context}"]
56+
[id="nodes-pods-autoscaling-custom-rn-2121-384-bugs_{context}"]
5757
=== Bug fixes
5858

59-
* Previously, if invalid values, such as nonexistent namespaces, were specified in scaled object metadata, the underlying scaler clients would not free, or close, their client descriptors, resulting in a slow memory leak. This fix properly closes the underlying client descriptors when there are errors, preventing memory from leaking. (link:https://issues.redhat.com/browse/OCPBUGS-30145[*OCPBUGS-30145*])
60-
61-
* Previously the `ServiceMonitor` custom resource (CR) for the `keda-metrics-apiserver` pod was not functioning, because the CR referenced an incorrect metrics port name of `http`. This fix corrects the `ServiceMonitor` CR to reference the proper port name of `metrics`. As a result, the Service Monitor functions properly. (link:https://issues.redhat.com/browse/OCPBUGS-25806[*OCPBUGS-25806*])
59+
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images were missing time zone information. As a consequence, scaled objects with `cron` triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds are updated to include time zone information. As a result, scaled objects containing `cron` triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-32395[*OCPBUGS-32395*])

0 commit comments

Comments
 (0)