Component
core/messaging/rabbitmq
A RabbitMQ message broker speaking the AMQP protocol, persisting queues and messages durably. Exports its host and AMQP port to consumers via the uses topology. Self-hosted, it renders as a stateful workload with a persistent volume, by a Helm Recipe (Workload synthesis to native Kubernetes resources), a Compose Recipe (local development), and a controller-driven Helm Recipe that emits a RabbitmqCluster custom resource for the RabbitMQ Cluster Operator. Reach for the synthesis Recipe on a cluster that runs no RabbitMQ control plane, and for the controller-driven one where the control plane is in place and the cluster should own upgrades, rolling restarts and credential rotation. Broker access always requires credentials: on these Recipes the password slot is optional, and each falls back to a deterministic inline development default so the render stays reproducible. Reach for the rabbitmq-amazon-mq Recipes, on terraform and on CloudFormation, where the broker is an Amazon MQ broker in the operator's AWS account. Amazon MQ serves AMQP over TLS alone, on 5671, published as protocol amqps, and requires a password: a core/random-password attachment, without which the build halts. It runs RabbitMQ 4.3, 4.2 and 3.13, so the engine_version default halts there. The self-hosted brokers serve their own metrics, published with `values.metrics_enabled` true; the Amazon MQ Recipes halt on true.
来源
- 内容摘要
- sha256:f4c0aefbfcb8b053e435e79985622412924a5ffdd575b3b96dcb804ba583bff4
- 发布时间
- 2026-11-10T10:12:32Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/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:e0e8d7037c8e13c83e681972e42ec3e0bcaf2b0c1cf48b972365c9c6c3a50d28
此版本的引用
oci://hub.aggrega.ai/component/core/messaging/rabbitmq:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| user | string | user | 否 | Application user the broker provisions on startup. The matching password comes from the password credential slot. On Amazon MQ it is the broker's one administrative user, named with 2 to 100 letters, digits, dashes, periods and underscores; the Amazon MQ Recipes refuse any other name, and guest. |
| metrics_enabled | boolean | false | 否 | Publishes where the broker's own metrics are, in the Prometheus format — the address as `metrics_endpoint`, or, on a controller-driven cluster of more than one node, the Service a scraper discovers every node behind — putting their port on the Service where a realization needs it; while false those keys are empty. The metrics port checks no caller, so anything that reaches it can read them. The Amazon MQ realizations halt the build on true, since the service shows its metrics only to a scraper presenting the broker's own credentials. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 5672 | 否 | AMQP listen port. Most operators should omit this and let the Recipe assign the default (5672). The Amazon MQ realizations do not read it — the service serves AMQP over TLS on 5671 alone, which they publish as port — and halt the build on any value other than this default. |
| management_port | integer (min 1024, max 65535) | 15672 | 否 | Management HTTP API and dashboard port. Most operators should omit this and let the Recipe assign the default (15672). The Amazon MQ realizations do not read it — the service serves the management interface at an address of its own — and halt the build on any value other than this default. |
| engine_version | string | 4.1.3-management-alpine | 否 | RabbitMQ container image tag. Selects the image tag on container targets. On Amazon MQ the major and minor version it begins with is the broker's RabbitMQ version, one of 4.3, 4.2 (both on the mq.m7g instance types alone) and 3.13; this default begins 4.1, which the service does not run, so the Amazon MQ realizations halt on it, naming the versions to set. |
| compute | object | — | 否 | — |
| storage | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
| control_plane_present | boolean | false | 否 | Operator affirmation that the RabbitMQ Cluster Operator (control plane) is installed in the target cluster. A controller-driven realization halts the build unless this is set true, so a RabbitmqCluster custom resource is never emitted as an orphan into a cluster that cannot reconcile it. The synthesized realizations ignore this flag. The Amazon MQ realizations do not read it and halt the build while it is true: no RabbitMQ control plane is installed for Amazon MQ. |
| credentials | string (generated | supplied) | generated | 否 | Who owns the broker's credentials on a controller-driven realization. `generated` — the controller creates the credential Secret and owns the password, which is what it does when nothing is supplied; the developer's `user` value is still honored, and no password reaches the rendered artifact. `supplied` — the controller reads the credentials from an existing Secret named in `credentials_secret` and generates none. The synthesized realizations ignore this key: they always take the password from the `password` credential slot. The Amazon MQ realizations do not read it either, and halt the build on `supplied`. |
| credentials_secret | string | 否 | Name of the existing Secret a controller-driven realization reads the broker credentials from when `credentials` is `supplied`. The Secret lives in the same namespace as the broker and carries the same entries the controller would otherwise generate — `username`, `password`, `default_user.conf`, `host`, `port`, `provider` and `type`. Leave it empty when `credentials` is `generated`; a controller-driven build halts if `supplied` is selected without it. The Amazon MQ realizations do not read it and halt the build while it is set. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | Address a producer or consumer opens its broker connection to. Which Service carries it follows the realization the Manifest selected, so a consumer reads this rather than deriving a name. On Amazon MQ it is a pointer string the target resolves to the host of the broker's AMQP endpoint — a Terraform reference, or a CloudFormation intrinsic that a consumer in another stack imports — or the DNS name the Release sets in infra.overrides.host instead, so a consumer on another target receives an address it can resolve. The broker's certificate names its own endpoint, so a client checking it fails against that DNS name. |
| port | integer | — | 是 | TCP port the broker accepts client connections on. It carries the messaging port, never the management API port, so a consumer reaches the broker rather than its dashboard; on Amazon MQ it is 5671. |
| protocol | string | — | 否 | Wire protocol the published address speaks, which is what a consumer selects a client library and its connection security for — `amqp`, AMQP without TLS, from the self-hosted realizations, and `amqps`, AMQP over TLS, from the Amazon MQ realizations, since the service requires TLS on every client connection. |
| metrics_endpoint | string | — | 否 | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:15692/metrics`. Empty while values.metrics_enabled is false, and on the controller-driven realization while the cluster runs more than one node, which then publishes `metrics_service` instead. |
| metrics_service | string | — | 否 | Name of the Service every node's metrics sit behind, for a scraper that discovers each endpoint of that Service rather than scraping one address. Set by the controller-driven realization while values.metrics_enabled is true and the cluster runs more than one node, beside `metrics_service_port` and `metrics_path`; empty otherwise. |
| metrics_service_port | string | — | 否 | Name of the port of `metrics_service` that carries the metrics, `prometheus`. Set and empty together with `metrics_service`. |
| metrics_path | string | — | 否 | Path the metrics are served at, `/metrics`, published beside `metrics_service`. Empty where the component publishes `metrics_endpoint`, which carries its own path. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| password | feature.aggrega.ai/kind=secret | 否 | env | 是 | Broker password credential. Attached, it supplies the RabbitMQ application-user password via the credential subsystem. Unattached, compose/rabbitmq and helm/rabbitmq set it to the development literal `devpass`, which this catalog publishes, so every Release built with them that leaves the slot unattached shares that password, and the Amazon MQ Recipes halt the build: they take core/random-password alone, with values.symbols false and values.length 12 or more, as Amazon MQ refuses a password shorter than 12 characters or holding a comma, colon or equals sign. |
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
此实体未使用目录中的任何内容。
被使用
使用套接字 «target_messaging»
使用套接字 «backend»
使用套接字 «databases»
使用套接字 «etcd»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «forward_target»
使用套接字 «scrape_target»
使用套接字 «backend»
使用套接字 «database»
适用于
适用于
适用于
实现
实现
实现
实现
实现