Skip to content

docs: explain KEDA automatic scaler discovery - #6892

Open
aryanbarde80 wants to merge 1 commit into
apache:mainfrom
aryanbarde80:docs/6891-keda-auto-discovery
Open

aryanbarde80 wants to merge 1 commit into
apache:mainfrom
aryanbarde80:docs/6891-keda-auto-discovery

Conversation

@aryanbarde80

Copy link
Copy Markdown

Problem

The KEDA trait reference documents the keda.auto option but does not explain how automatic discovery works, what a KEDA scaler is, or which Camel components currently have automatic scaler mappings. This makes it difficult for users to understand what auto will and will not configure.

Solution

  • Add an “Automatic scaler discovery” section to the KEDA trait reference.
  • Explain how Camel K derives KEDA triggers from consumer endpoint URIs.
  • Document the currently supported automatic mapping: kafka.
  • Link to the KEDA scaler concepts and Apache Kafka scaler documentation.
  • Clarify that unsupported components can still use explicit keda.triggers configuration.

The new section is outside the autogenerated configuration block, so no generated content was manually modified.

Testing

  • git diff --check — passed.
  • make update-docs — attempted, but could not complete because the contributor environment does not have the required go and yq executables.
  • The generated page was restored afterward, and the final diff was verified to contain only the intended documentation change.

Fixes #6891

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a section in KEDA trait page to explain what to expect when using "auto"

1 participant