Component
core/compute/knative-serving
The Knative Serving control plane, declared as an explicit component so a scale-to-zero realization ships its runtime prerequisite alongside the custom resources it emits. Its controllers reconcile Service, Configuration, Revision and Route into Deployments, hold requests for a revision at zero replicas, and set replica count from observed concurrency. Declaring it in that same Aggregate is what satisfies the prerequisite. Realized on Kubernetes via its Helm Recipe, a minimal bootstrap installing the four control-plane workloads and neither the custom-resource definitions nor the ingress layer. What it publishes across an edge is where Prometheus finds its own metrics, which are off by default. With `values.metrics_enabled` true the Recipe switches them on, and each of the four processes serves them in pods of its own, on a port no Service carries, so the Recipe publishes the pod label selecting all four, the name of their metrics port and the path, for a scraper that discovers those pods directly; false, those keys are empty.
Procedencia
- Digest del contenido
- sha256:7cebf451f2fd01bccecb5c83c4ec8a7f9d919f013928459ed34a229bf886af7f
- Publicado
- 2026-11-10T10:10:13Z
- 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:a6b83b0e1dbb988835259ae55af82c3a7a93abb719ac8bb76e8dc39b8decbeb1
Referencia en esta versión
oci://hub.aggrega.ai/component/core/compute/knative-serving:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| metrics_enabled | boolean | false | no | Switches on the control plane's own metrics, in the Prometheus format, and publishes the pod label, the port name and the path a scraper discovers them by; while false those keys are empty. The metrics port checks no caller, so anything that reaches the control plane's pods can read them. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| namespace | string | knative-serving | no | Namespace the control plane is installed into and watches. |
| controller_image | string | gcr.io/knative-releases/knative.dev/serving/cmd/controller@sha256:ca5062ece0329d002a81940cf4268d7898866434d70049bb93f27d3a786d3292 | no | Image the controller Deployment runs. The controller reconciles the Serving custom resources into Deployments and serverless services. |
| webhook_image | string | gcr.io/knative-releases/knative.dev/serving/cmd/webhook@sha256:3846e9a416665c5b9ec2e4de246cfcb5c4ab0d01ba19348aa008caf30144b650 | no | Image the webhook Deployment runs. The webhook defaults and validates the Serving custom resources as they are admitted. |
| autoscaler_image | string | gcr.io/knative-releases/knative.dev/serving/cmd/autoscaler@sha256:879da127b23db65d862cafa6b23fb987381d0e44150f0027d44e1f5aee83bde2 | no | Image the autoscaler Deployment runs. The autoscaler decides each revision's replica count, zero included, from reported concurrency. |
| activator_image | string | gcr.io/knative-releases/knative.dev/serving/cmd/activator@sha256:e5ab46f3b73fa2e3898fe47f6a3a0c2bd765596f4fb36ceb4c28c35d0a74b2e5 | no | Image the activator Deployment runs. The activator holds requests addressed to a revision at zero replicas and reports the concurrency the autoscaler scales on. |
| queue_proxy_image | string | gcr.io/knative-releases/knative.dev/serving/cmd/queue@sha256:a3cc71ce80dbc6df8781f15eac2cf3531a4c9815271799afd8776bef9e6aeaf2 | no | Image the controller stamps into each revision as its request-queue sidecar. The sidecar meters concurrency for the autoscaler and queues requests beyond the revision's configured limit. |
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_pod_selector | string | — | no | Kubernetes label selector matching the controller, webhook, autoscaler and activator pods, `app.kubernetes.io/name=knative-serving`, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path` while values.metrics_enabled is true; empty otherwise. |
| metrics_pod_port | string | — | no | Name of the container port on those pods that carries the metrics, `metrics`. Set and empty together with `metrics_pod_selector`. |
| metrics_path | string | — | no | Path the metrics are served at on that port, `/metrics`. Set and empty together with `metrics_pod_selector`. |
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