This is an automated email from the ASF dual-hosted git repository.
squakez pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 9c0772f93 docs: explain KEDA automatic scaler discovery
9c0772f93 is described below
commit 9c0772f93451313bd7dc4d184c85d2953bcb6320
Author: aryanbarde80 <[email protected]>
AuthorDate: Sun Oct 18 08:32:46 2026 +0000
docs: explain KEDA automatic scaler discovery
---
docs/modules/traits/pages/keda.adoc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/docs/modules/traits/pages/keda.adoc
b/docs/modules/traits/pages/keda.adoc
index 5f01467ce..13fddb354 100644
--- a/docs/modules/traits/pages/keda.adoc
+++ b/docs/modules/traits/pages/keda.adoc
@@ -68,3 +68,13 @@ NOTE: the variable names are "snake case" if you're using in
`kamel` CLI, for ex
// End of autogenerated code - DO NOT EDIT! (configuration)
+
+== Automatic scaler discovery
+
+When `keda.auto` is enabled, Camel K inspects the consumer endpoints in an
Integration and creates KEDA triggers for components with a registered scaler
mapping. A scaler is the KEDA adapter that reads metrics from an external
system and uses them to determine when a workload should scale. See the
https://keda.sh/docs/latest/concepts/scaling-deployments/[KEDA scaler concepts]
documentation for more information.
+
+Automatic discovery currently supports the following Camel component:
+
+* `kafka`: creates an Apache Kafka trigger from the topic, broker, and
consumer-group values in the endpoint URI. See the
https://keda.sh/docs/latest/scalers/apache-kafka/[KEDA Apache Kafka scaler]
documentation for the available trigger metadata.
+
+Unsupported Camel components do not produce an automatically discovered
trigger. You can still configure their KEDA triggers explicitly with
`keda.triggers`.
