Component

core/datastore/mariadb-operator

The mariadb-operator control plane, declared as an explicit component so a controller-driven MariaDB realization can ship its runtime prerequisite alongside the MariaDB custom resource it emits, rather than assuming an ambient install. The control plane is the controller that reconciles MariaDB custom resources into running database servers, their client Services and their credential Secrets. Declare this component in the same Aggregate as a controller-driven MariaDB to satisfy the MariaDB component's control-plane prerequisite; the operator affirms the prerequisite on the database in the same Release. Realized on Kubernetes by two Helm Recipes. `mariadb-operator-chart` renders the project's own chart, custom-resource definitions, certificate controller and admission webhook included: reach for it for a full install, where the chart repository is reachable from the build. `mariadb-operator` is a minimal bootstrap installing the controller alone: reach for it where the definitions are already installed in the cluster and the build must fetch nothing. The controller 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:c87a718fcb6e34dba2c54ef980c2ab1f1c2b410c53eaac8ab1bc1dfa3a4acae4
Published
2026-11-10T10:10:43Z
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:5fc4b0616f420c5f17330d3d7b6ef0d1c473e28f09ff6918e2855df1c3802ddc

Reference at this version

oci://hub.aggrega.ai/component/core/datastore/mariadb-operator:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
metrics_enabledbooleanfalsenoPublishes the address of the controller'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 metrics port checks no caller, so anything that reaches it can read them.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestringghcr.io/mariadb-operator/mariadb-operator:26.10.0nomariadb-operator image the control-plane Deployment runs. Pinned to a release tag so the rendered workload references an immutable version.
namespacestringmariadb-systemnoNamespace the control plane is installed into. It watches MariaDB custom resources across the whole cluster, so this names where the controller runs rather than what it reconciles. The `mariadb-operator-chart` realization requires the Release to declare the same namespace for the component.
source_versionstring—noVersion of the mariadb-operator chart the `mariadb-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