Component

core/compute/keda

The KEDA control plane, declared as an explicit component so an event-driven realization ships its runtime prerequisite alongside the custom resources it emits. Its operator reconciles ScaledObject and ScaledJob into horizontal pod autoscalers, and its metrics adapter answers the external-metrics API, so a workload scales on queue depth or event rate down to zero. Declaring it in that same Aggregate satisfies the prerequisite. Realized on Kubernetes by two Helm Recipes. `keda-chart` renders the project's own chart, custom-resource definitions and admission webhooks included, and is the one to reach for; its chart repository must be reachable from the build. `keda` is a minimal bootstrap installing the operator and adapter without the definitions or the webhooks, and at the images pinned here neither process starts, because it sets no WATCH_NAMESPACE. What it publishes across an edge is where Prometheus finds its own metrics. The operator and the adapter each serve them behind a Service of their own, under names fixed for the cluster, so each Recipe publishes both Service names, the name of their metrics port and the path, for a scraper that discovers every endpoint behind them.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:90c9637aafe678ca9a8364377341a97251826df17666ad6f7f0908f19bba29fd
Published
2026-11-10T10:10:09Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:5d6213c1921a109b2734c8b07d53ab46b55f051b9f8d70f2a98929552026a0ae

Reference at this version

oci://hub.aggrega.ai/component/core/compute/keda:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

No developer parameters declared.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
namespacestringkedanoNamespace the control plane is installed into. The `keda-chart` realization requires the Release to declare the same namespace for the component.
source_versionstring—noVersion of the KEDA chart the `keda-chart` realization pulls. Its default is the release whose application version is the tag of the two image defaults below; changing it away from that default does not guarantee value-mapping compatibility with the new chart, and the images follow it only where they are set too.
overridesobject (open)—noProvider-specific overrides; each Recipe documents the keys it reads.
operator_imagestringghcr.io/kedacore/keda:2.20.2noImage the operator Deployment runs. The operator reconciles the scaling custom resources into horizontal pod autoscalers and issues the certificate the metrics adapter serves on.
metrics_adapter_imagestringghcr.io/kedacore/keda-metrics-apiserver:2.20.2noImage the metrics adapter Deployment runs. The adapter answers the cluster's external-metrics API on behalf of the horizontal pod autoscalers the operator creates.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
metrics_servicestring—noNames of the Services the operator's and the metrics adapter's metrics sit behind, comma-separated — `keda-operator,keda-metrics-apiserver` from the bootstrap, `keda-operator,keda-operator-metrics-apiserver` from the chart — for a scraper that discovers each endpoint of those Services rather than scraping one address. Published beside `metrics_service_port` and `metrics_path`.
metrics_service_portstring—noName of the port of both Services that carries the metrics, `metrics`.
metrics_pathstring—noPath the metrics are served at on that port, `/metrics`.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy