Component
core/messaging/kafka
An Apache Kafka event-streaming broker in KRaft mode, with no ZooKeeper, keeping its commit log on durable storage, so it renders as a stateful server. Its primary contract to consumers is the client bootstrap endpoint: a producer or consumer wires to it, through `host` and `port` or the `bootstrap_servers` list, and reaches the cluster there. Realized on Kubernetes two ways, both through Helm Recipes and chosen in the Manifest: a synthesis Recipe that builds one node, running the broker and controller roles in one process, from the official Apache Kafka image, and a controller-driven Recipe that emits a Kafka custom resource for the Strimzi Cluster Operator to reconcile. Reach for the synthesis Recipe on a cluster that runs no Kafka control plane — it needs no operator installed and no chart repository, so it builds with nothing fetched — and for the controller-driven Recipe where the Strimzi Cluster Operator is already in place and the cluster should own broker upgrades, rolling restarts and partition rebalancing; it runs Kafka 4.2.0 to 4.3.1 only, which the `engine_version` default is not. Reach for terraform/kafka-msk where Kafka is an Amazon MSK cluster in the operator's AWS account: two or three brokers, one per client subnet, serving plaintext on 9092 inside the VPC, or TLS on 9094. There is no Compose realization, and no CloudFormation one: a stack reads no bootstrap address off an MSK cluster without running code of its own. `infra.client_tls`, off by default, serves clients TLS alone and publishes `protocol` `kafka-ssl`: the synthesized broker presents the certificate attached to `server_certificate`, Strimzi one its cluster authority issues, MSK one AWS issues.
출처
- 콘텐츠 다이제스트
- sha256:a17a606a9df7d91ff68b87ff8dd99f611a3fdb195c1104a6fd65070a01011d37
- 게시일
- 2026-11-10T10:12:25Z
- 서명 ID
- 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:fc7be806070c32bac4e3a6f89f6defad3cf1bbe71d5b105146497c93acc71af2
이 버전의 참조
oci://hub.aggrega.ai/component/core/messaging/kafka:1.0.0개발자 매개변수
개발자가 Aggregate에서 설정하는 값입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| cluster_id | string | 4L6g3nShT-eMCtK--X86sw | 아니요 | Pinned KRaft cluster identity; a fixed value keeps the render deterministic. Honoured by the synthesized realization; on the controller-driven one the operator generates the identity, and on MSK the service does, so neither reads it and each halts the build on any value other than this default. |
| metrics_enabled | boolean | false | 아니요 | Turns on the brokers' own metrics, in the Prometheus format, on a port of their own on every node, and publishes the pod label selector, port name and path a scraper discovers them by; while false those keys are empty. The port checks no caller, so anything that reaches a node can read them. Honored by the controller-driven realization; the synthesized one serves no Prometheus metrics, and MSK runs no pod these keys could name, so both halt the build when this is true. |
운영자 사이징
운영자가 환경별로 조정하는 인프라 사이징입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| broker_port | integer | 9092 | 아니요 | Client bootstrap port — the endpoint producers and consumers connect to. MSK fixes its ports itself, serving plaintext on 9092 and, while infra.client_tls is true, TLS on 9094, which its realization publishes as port; so the MSK realization halts the build on any value other than this default. |
| client_tls | boolean | false | 아니요 | Serve client connections over TLS alone. Off by default, which serves plaintext and renders exactly as a broker without the setting. On, the client listener accepts TLS alone on the published host and port, requests no client certificate, and the published `protocol` is `kafka-ssl`. The synthesized realization presents the certificate attached to `server_certificate` (required while this is on). The controller-driven realization presents one the Strimzi cluster certificate authority issues, or the one attached to `server_certificate`; a consumer trusts the authority's certificate, `ca.crt` in the Secret `<cluster>-cluster-ca-cert`, through its `server_ca`. On MSK it turns client-broker encryption in transit to TLS alone, on port 9094, whose certificate AWS issues and clients trust without a `server_ca`; that certificate does not name a DNS name the Release sets in `infra.overrides.host`, so the MSK realization halts on the two together. The controller quorum is unchanged. |
| controller_port | integer | 9093 | 아니요 | Internal KRaft controller-quorum port. Not part of the exported contract. Honoured by the synthesized realization; on the controller-driven one the operator fixes the port, and on MSK the controllers are the service's own, so neither reads it and each halts the build on any value other than this default. |
| engine_version | string | 4.1.2 | 아니요 | Apache Kafka image tag. Pins the packaged Kafka version the workload references. On the controller-driven realization it is the Kafka version the operator runs, one of 4.2.0 to 4.3.1, which this default is not. On MSK the major and minor version it begins with (4.1 from this default) is the cluster's Kafka version, one of 3.8, 3.9, 4.0 and 4.1, and any other halts the build naming them. |
| storage | object | — | 아니요 | — |
| compute | 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 Kafka operator (control plane) is installed in the target cluster. An operator-driven realization halts the build unless this is set true, so a Kafka custom resource is never emitted as an orphan into a cluster that cannot reconcile it. The synthesized StatefulSet realization ignores this flag. The MSK realization does not read it and halts the build while it is true: no Kafka control plane is installed for MSK. |
출력 계약
이 컴포넌트가 uses 토폴로지를 통해 소비자에게 게시하는 값입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| host | string | — | 예 | Bootstrap address a producer or consumer connects to first, from which the client learns the rest of the cluster. Which Service carries it follows the realization the Manifest selected, so a consumer reads this rather than deriving a name. On MSK it is a pointer string Terraform resolves to the first broker of the bootstrap list, or the DNS name the Release sets in infra.overrides.host instead, so a consumer on another target receives an address it can resolve. |
| port | integer | — | 예 | TCP port the bootstrap address accepts client connections on. It carries the broker port an operator set, never the controller-quorum port, which is internal to the cluster; on MSK it is 9092, or 9094 while infra.client_tls is true. |
| bootstrap_servers | string | — | 예 | Comma-separated `host:port` list a Kafka client takes as its bootstrap servers — what a client that takes a list reads, where `host` and `port` serve one that takes a single address. A realization with one bootstrap address publishes that address as the whole list. On MSK it is a pointer string Terraform resolves to every broker, or the infra.overrides.host name with the port while the Release sets one; a consumer on another target receives the pointer as text. |
| protocol | string | — | 아니요 | Wire protocol the published address speaks, which is what a consumer selects a client library and its connection security for, on every realization — `kafka` while `infra.client_tls` is off, and `kafka-ssl` while it is on, when the address accepts TLS connections alone: a Kafka client then sets its `security.protocol` to `SSL`. A client that reads only `host` and `port` reads this key too to learn that TLS is required: a plaintext client reaching a TLS listener fails its handshake and exchanges no record. |
| metrics_pod_selector | string | — | 아니요 | Kubernetes label selector matching every Kafka node pod, for a scraper that discovers those pods directly. Set by the controller-driven realization while values.metrics_enabled is true, beside `metrics_pod_port` and `metrics_path`; empty otherwise. |
| metrics_pod_port | string | — | 아니요 | Name of the container port on those pods that carries the metrics, `tcp-prometheus`. Set and empty together with `metrics_pod_selector`. |
| metrics_path | string | — | 아니요 | Path the metrics are served at on that port, `/metrics`. Set and empty together with `metrics_pod_selector`. |
uses 소켓
이 컴포넌트가 연결에 사용하는 의존성 소켓입니다. 소켓을 통해 배선되는 모든 연결의 대상은 해당 소켓의 레이블 셀렉터를 충족해야 하며, 각 연결은 소켓이 선언한 슬롯에 첨부를 전달할 수 있습니다. 필수 슬롯은 Aggregate 또는 Release가 해당 소켓을 통해 배선하는 각 연결이 채워야 합니다.
선언된 uses 소켓이 없습니다.
첨부 슬롯
Feature가 이 컴포넌트에 첨부되는 이름 있는 바인딩 지점입니다. 슬롯의 셀렉터는 어떤 Feature가 슬롯을 채울 수 있는지를 제한하고, 슬롯의 inject 목록은 Feature의 자료를 어떻게 전달할 수 있는지를 지정합니다. 필수 슬롯은 인스턴스의 첨부 또는 그 위 범위의 첨부를 통해 모든 인스턴스에서 바인딩되어야 하며, 민감 슬롯은 비밀 자료를 처리하도록 선언됩니다. Feature는 어떤 슬롯도 선언하지 않은 이름으로 첨부될 수도 있습니다.
| 슬롯 | 셀렉터 | 필수 | 주입 | 민감 | 설명 |
|---|---|---|---|---|---|
| server_certificate | feature.aggrega.ai/kind=secret | 아니요 | file | 예 | Optional certificate the broker presents to its clients while infra.client_tls is true: a Secret holding tls.crt, the certificate followed by any intermediate certificates, and tls.key, its private key, the two keys a kubernetes.io/tls Secret holds, the key unencrypted in PKCS #8 form (BEGIN PRIVATE KEY), the one form Kafka reads. The certificate names every address a client dials: the published host, and its namespace-qualified forms where clients in other namespaces connect; on the controller-driven realization a client also dials each broker under <instance>-kafka-brokers, beside the published <instance>-kafka-bootstrap, so the certificate also names *.<instance>-kafka-brokers and its namespace-qualified forms. Mounted as files, so attach a Feature that names an existing Secret, such as core/referenced-secret. Required by the synthesized realization while client_tls is true; the controller-driven one presents it in place of the certificate the Strimzi cluster authority issues, from a Secret in the Kafka resource's namespace. A build halts on it attached while client_tls is false. MSK presents a certificate AWS issues, so its realization halts on any attachment here. |
자체 주입 허용 목록
선언된 자체 주입 파이프가 없습니다.
관계
게시된 다른 엔터티와 주고받는 타입 지정 에지입니다. 게시된 대상이 없는 참조는 링크가 아닌 끊어진 에지로 표시됩니다.
사용함
이 엔터티는 카탈로그의 어떤 것도 사용하지 않습니다.
사용됨
소켓 «target_messaging» 사용
소켓 «backend» 사용
소켓 «databases» 사용
소켓 «etcd» 사용
소켓 «backend» 사용
소켓 «backend» 사용
소켓 «forward_target» 사용
소켓 «scrape_target» 사용
소켓 «backend» 사용
소켓 «database» 사용
적용 대상
적용 대상
적용 대상
구현
구현
구현