Documentation·
apache/camel-k
Clarify KEDA automatic scaler discovery and Kafka mapping
The KEDA trait reference now explains how Camel K discovers scaling triggers from Integration consumer endpoints. It documents Kafka as the currently supported automatic mapping and identifies explicit trigger configuration as the alternative for unsupported components.
The problem
The reference documented `keda.auto` without explaining scaler concepts or how automatic discovery derives triggers. It also omitted which Camel components have automatic mappings, leaving the boundaries of automatic configuration unclear.
The approach
Added an “Automatic scaler discovery” section outside the autogenerated configuration block. The section defines a KEDA scaler and explains that registered component mappings produce triggers from consumer endpoints. It details the Kafka mapping's topic, broker, and consumer-group URI values, links to KEDA documentation, and describes the `keda.triggers` alternative.
What changed
The reference now states that automatic discovery supports `kafka`, unsupported components do not produce automatically discovered triggers, and triggers can still be configured explicitly. No runtime behavior or autogenerated configuration content was changed.
- keda
- kafka
- autoscaling
- camel-k
- documentation