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.
Procedencia
- Digest del contenido
- sha256:90c9637aafe678ca9a8364377341a97251826df17666ad6f7f0908f19bba29fd
- Publicado
- 2026-11-10T10:10:09Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/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
Referencia en esta versión
oci://hub.aggrega.ai/component/core/compute/keda:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
No se declararon parámetros del desarrollador.
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| namespace | string | keda | no | Namespace the control plane is installed into. The `keda-chart` realization requires the Release to declare the same namespace for the component. |
| source_version | string | — | no | Version 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. |
| overrides | object (open) | — | no | Provider-specific overrides; each Recipe documents the keys it reads. |
| operator_image | string | ghcr.io/kedacore/keda:2.20.2 | no | Image 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_image | string | ghcr.io/kedacore/keda-metrics-apiserver:2.20.2 | no | Image the metrics adapter Deployment runs. The adapter answers the cluster's external-metrics API on behalf of the horizontal pod autoscalers the operator creates. |
Contrato de salida
Valores que este componente publica para los consumidores a través de la topología uses.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| metrics_service | string | — | no | Names 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_port | string | — | no | Name of the port of both Services that carries the metrics, `metrics`. |
| metrics_path | string | — | no | Path the metrics are served at on that port, `/metrics`. |
Sockets uses
Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.
No se declararon sockets uses.
Slots de acoplamiento
Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.
No se declararon slots de acoplamiento.
Lista de permitidos de autoinyección
No se declararon canales de autoinyección.
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
Esta entidad no usa nada del catálogo.
Usado por
usa el socket «upstream»
usa el socket «forward_target»
usa el socket «scrape_target»
usa el socket «store»
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
se aplica a
implementa
implementa