Component

core/messaging/strimzi-operator

The Strimzi Cluster Operator, declared as an explicit component so an operator-driven Kafka realization can ship its runtime prerequisite alongside the Kafka custom resource it emits, rather than assuming an ambient install. The control plane is the operator that reconciles Kafka custom resources into running brokers. Declare this component in the same Aggregate as an operator-driven Kafka to satisfy the Kafka component's control-plane prerequisite; the operator affirms the prerequisite on the Kafka in the same Release. Realized on Kubernetes by two Helm Recipes. `strimzi-operator-chart` renders the project's own chart, custom-resource definitions and the operator's full roles included, and is the one to reach for; its chart repository must be reachable from the build. `strimzi-operator` is a minimal bootstrap installing the operator alone, and at the image pinned here its role falls short of what the operator needs to run a Kafka cluster. The operator serves its own metrics on its pod. With `values.metrics_enabled` true each Recipe puts their port on a ClusterIP Service in the control plane's namespace and publishes the address as `metrics_endpoint`; false, that key is empty.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:8bf26802ab372e624522555204968e1870b3b6bec8cc5ce05280e7c2cd93d032
Published
2026-11-10T10:12:33Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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:1f157751f95b4b3dae8fbd9da58e743925c5a6a27e69395ce03f69869db81219

Reference at this version

oci://hub.aggrega.ai/component/core/messaging/strimzi-operator:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
metrics_enabledbooleanfalsenoPublishes the address of the operator's own metrics, in the Prometheus format, as `metrics_endpoint`, putting their port on a ClusterIP Service of its own; while false that key is empty. The port, which also answers the operator's liveness and readiness paths, checks no caller, so anything that reaches it can read them.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestringquay.io/strimzi/operator:1.3.0noStrimzi Cluster Operator image the control-plane Deployment runs. Pinned to a published release tag so the rendered workload names one version; a Release pulling from its own registry mirror sets this to that reference instead.
namespacestringkafkanoNamespace the control plane is installed into and watches. The `strimzi-operator-chart` realization requires the Release to declare the same namespace for the component.
source_versionstring—noVersion of the Strimzi chart the `strimzi-operator-chart` realization pulls. Its default is the release whose application version is the tag of the image default above; changing it away from that default does not guarantee value-mapping compatibility with the new chart, and the image follows it only where it is set too.
overridesobject (open)—noProvider-specific overrides; each Recipe documents the keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>.<namespace>:8080/metrics`, the host qualified with the namespace the control plane runs in. Empty while values.metrics_enabled is false.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy