Skip to content

Commit 0e3332f

Browse files
authored
Merge pull request #61855 from mburke5678/cma-2.10.1-263
CMA Adding 2.10.1-267 Release Notes
2 parents 3a87799 + 30f6db1 commit 0e3332f

File tree

1 file changed

+26
-5
lines changed

1 file changed

+26
-5
lines changed

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

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,31 +30,52 @@ The following table defines the Custom Metrics Autoscaler Operator versions for
3030
|{product-title} version
3131
|General availability
3232

33-
|2.10.1
33+
|2.10.1-267
3434
|4.13
3535
|General availability
3636

37-
|2.10.1
37+
|2.10.1-267
3838
|4.12
3939
|General availability
4040

41-
|2.10.1
41+
|2.10.1-267
4242
|4.11
4343
|General availability
4444

45-
|2.10.1
45+
|2.10.1-267
4646
|4.10
4747
|General availability
4848
|===
4949

50+
[id="nodes-pods-autoscaling-custom-rn-210-267_{context}"]
51+
== Custom Metrics Autoscaler Operator 2.10.1-267 release notes
52+
53+
This release of the Custom Metrics Autoscaler Operator 2.10.1-267 provides new features and bug fixes for running the Operator in an {product-title} cluster. The components of the Custom Metrics Autoscaler Operator 2.10.1-267 were released in link:https://access.redhat.com/errata/RHBA-2023:4089[RHBA-2023:4089].
54+
55+
[IMPORTANT]
56+
====
57+
Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of KEDA.
58+
====
59+
60+
[id="nodes-pods-autoscaling-custom-rn-210-267-bugs_{context}"]
61+
=== Bug fixes
62+
63+
* Previously, the `custom-metrics-autoscaler` and `custom-metrics-autoscaler-adapter` images did not contain time zone information. Because of this, scaled objects with cron triggers failed to work because the controllers were unable to find time zone information. With this fix, the image builds now include time zone information. As a result, scaled objects containing cron triggers now function properly. (link:https://issues.redhat.com/browse/OCPBUGS-15264[*OCPBUGS-15264*])
64+
65+
* Previously, the Custom Metrics Autoscaler Operator would attempt to take ownership of all managed objects, including objects in other namespaces and cluster-scoped objects. Because of this, the Custom Metrics Autoscaler Operator was unable to create the role binding for reading the credentials necessary to be an API server. This caused errors in the `kube-system` namespace. With this fix, the Custom Metrics Autoscaler Operator skips adding the `ownerReference` field to any object in another namespace or any cluster-scoped object. As a result, the role binding is now created without any errors. (link:https://issues.redhat.com/browse/OCPBUGS-15038[*OCPBUGS-15038*])
66+
67+
* Previously, the Custom Metrics Autoscaler Operator added an `ownerReferences` field to the `openshift-keda` namespace. While this did not cause functionality problems, the presence of this field could have caused confusion for cluster administrators. With this fix, the Custom Metrics Autoscaler Operator does not add the `ownerReference` field to the `openshift-keda` namespace. As a result, the `openshift-keda` namespace no longer has a superfluous `ownerReference` field. (link:https://issues.redhat.com/browse/OCPBUGS-15293[*OCPBUGS-15293*])
68+
69+
* Previously, if you used a Prometheus trigger configured with authentication method other than pod identity, and the `podIdentity` parameter was set to `none`, the trigger would fail to scale. With this fix, the Custom Metrics Autoscaler for OpenShift now properly handles the `none` pod identity provider type. As a result, a Prometheus trigger configured with authentication method other than pod identity, and the `podIdentity` parameter sset to `none` now properly scales. (link:https://issues.redhat.com/browse/OCPBUGS-15274[*OCPBUGS-15274*])
70+
5071
[id="nodes-pods-autoscaling-custom-rn-210_{context}"]
5172
== Custom Metrics Autoscaler Operator 2.10.1 release notes
5273

5374
This release of the Custom Metrics Autoscaler Operator 2.10.1 provides new features and bug fixes for running the Operator in an {product-title} cluster. The components of the Custom Metrics Autoscaler Operator 2.10.1 were released in link:https://access.redhat.com/errata/RHEA-2023:3199[RHEA-2023:3199].
5475

5576
[IMPORTANT]
5677
====
57-
Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously-installed Technology Preview versions or the community-supported version of KEDA.
78+
Before installing this version of the Custom Metrics Autoscaler Operator, remove any previously installed Technology Preview versions or the community-supported version of KEDA.
5879
====
5980

6081
[id="nodes-pods-autoscaling-custom-rn-210-new_{context}"]

0 commit comments

Comments
 (0)