Component
core/messaging/nats
A NATS messaging server for pub-sub, request-reply, and queueing. In this lean shape NATS routes subjects in memory with no durable persistence (JetStream file storage is not enabled), so the component renders as a stateless workload rather than a stateful one and declares no storage. Authentication is off by default; when a credential is attached to the optional password slot, each Recipe enables user/password authentication and wires the credential through the credential subsystem. Provider-agnostic: the same component is implemented by a Helm Recipe (Workload synthesis to native Kubernetes resources) and a Compose Recipe (local development). Exports its host and client port to consumers via the uses topology. On Kubernetes there are two realizations and the Manifest chooses between them. `nats` synthesizes the server as a workload and fetches nothing, so it is the one to reach for where the build must complete with no chart repository reachable. `nats-chart` renders the product's own Helm chart, which additionally carries a sidecar that reloads the server configuration in place, start-up, readiness and liveness probes against the monitoring endpoint, and a drain-then-shut-down sequence that lets connected clients move off before the pod goes away — and it is the realization that honours `monitoring_port`, so reach for it where a chart repository is reachable at build time.
Procedencia
- Digest del contenido
- sha256:6442f87145c50476deb4c047562136eece91faa7a3ebc101d7ec4458916f1e5e
- Publicado
- 2026-11-10T10:12:28Z
- 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:90bd8f7234f43e27af901a28509adea5872dc136a2a8965ba80f287a2ee77ce2
Referencia en esta versión
oci://hub.aggrega.ai/component/core/messaging/nats:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| user | string | nats_client | no | Client user provisioned for authenticated connections. Used only when a password credential is attached to the optional password slot; ignored when the server runs without authentication. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 4222 | no | Client listen port. Most operators should omit this and let the Recipe assign the default (4222). |
| monitoring_port | integer (min 1024, max 65535) | 8222 | no | HTTP monitoring endpoint port. Most operators should omit this and let the Recipe assign the default (8222). Read by the chart-backed realization, which serves the endpoint and aims its probes at it; the workload-synthesis and Compose realizations expose no monitoring endpoint and ignore it. |
| engine_version | string | 2.11-alpine | no | NATS container image tag. Selects the image tag on container targets; the chart-backed realization pins its own image tag. |
| source_version | string | — | no | Version of the Helm chart the chart-backed realization pulls. Read only by that realization; the workload-synthesis and Compose realizations pull no source artifact and ignore it. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
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 |
|---|---|---|---|---|
| host | string | — | sí | In-cluster DNS name of the Service fronting the server. A publisher or subscriber puts this name in its client's server list together with `port`. |
| port | integer | — | sí | TCP port the server accepts client connections on. It carries the client port an operator set, never the monitoring port. |
| protocol | string | — | no | Wire protocol the published address speaks — `nats`, which is what a consumer selects a client library for. |
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.
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| password | feature.aggrega.ai/kind=secret | no | env | sí | Optional server authentication credential. When attached, enables NATS user/password authentication and supplies the password; unattached, the server runs without authentication. |
Lista de permitidos de autoinyección
env
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 «media_server»
usa el socket «target_messaging»
usa el socket «upstream»
usa el socket «media_server»
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
implementa