Skip to content

Commit 6c250a7

Browse files
authored
Merge pull request #58230 from mburke5678/cma-add-kafka-tp
CMA add TP note for the Kafka scaler
2 parents 6b6fd17 + eb63103 commit 6c250a7

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

modules/nodes-pods-autoscaling-custom-trigger.adoc

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@
88

99
Triggers, also known as scalers, provide the metrics that the Custom Metrics Autoscaler Operator uses to scale your pods.
1010

11-
[NOTE]
12-
====
1311
The custom metrics autoscaler currently supports only the Prometheus, CPU, memory, and Apache Kafka triggers.
14-
====
12+
13+
:FeatureName: Autoscaling based on Apache Kafka metrics
14+
include::snippets/technology-preview.adoc[leveloffset=+0]
1515

1616
//You can specify a single trigger or multiple triggers. When using multiple triggers, the scaling is based on the greatest value from all the triggers. This section contains examples of the triggers supported for use with {product-title}.
1717

@@ -149,6 +149,9 @@ spec:
149149

150150
You can scale pods based on an Apache Kafka topic or other services that support the Kafka protocol. The custom metrics autoscaler does not scale higher than the number of Kafka partitions, unless you set the `allowIdleConsumers` parameter to `true` in the scaled object or scaled job.
151151

152+
:FeatureName: Autoscaling based on Apache Kafka metrics
153+
include::snippets/technology-preview.adoc[leveloffset=+0]
154+
152155
[NOTE]
153156
====
154157
If the number of consumer groups exceeds the number of partitions in a topic, the extra consumer groups sit idle.

nodes/pods/nodes-pods-autoscaling-custom.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,13 @@ include::snippets/technology-preview.adoc[]
1313

1414
The Custom Metrics Autoscaler Operator for Red Hat OpenShift is an optional operator, based on the Kubernetes Event Driven Autoscaler (KEDA), that allows workloads to be scaled using additional metrics sources other than pod metrics.
1515

16-
[NOTE]
17-
====
1816
The custom metrics autoscaler currently supports only the Prometheus, CPU, memory, and Apache Kafka metrics.
19-
====
2017

2118
// For example, you can scale a database application based on the number of tables in the database, scale another application based on the number of messages in a Kafka topic, or scale based on incoming HTTP requests collected by {product-title} monitoring.
2219

20+
:FeatureName: Autoscaling based on Apache Kafka metrics
21+
include::snippets/technology-preview.adoc[leveloffset=+0]
22+
2323
// The following include statements pull in the module files that comprise
2424
// the assembly. Include any combination of concept, procedure, or reference
2525
// modules required to cover the user story. You can also include other

0 commit comments

Comments
 (0)