Component
core/datastore/mariadb
A MariaDB relational database. Provider-agnostic: the same component is implemented by Helm Recipes (Workload synthesis to native Kubernetes resources), Terraform Recipes (AWS RDS), CloudFormation Recipes, Compose Recipes (local development), and a controller-driven Helm Recipe that emits a MariaDB custom resource for the mariadb-operator control plane to reconcile. Reach for the synthesis Recipe on a cluster that runs no MariaDB control plane — it needs no controller installed and no chart repository, so it builds with nothing fetched — and for the controller-driven Recipe where the control plane is already in place and the cluster should own upgrades, rolling restarts, credential rotation and, through infra.ha, replication and failover. On AWS RDS through Terraform, reach for terraform/mariadb-rds-terraform-aws-modules, which vendors the terraform-aws-modules project's published RDS module, where the pull may fetch it from its git repository; reach for terraform/mariadb-rds, which authors its own body, or terraform/mariadb-rds-module, which vendors a module kept beside it, where nothing may be fetched, and for terraform/mariadb-rds where read replicas are needed. Backup is the core/backup attachment, written in the Release. The managed Recipes configure the service's own automated backups from it, bound to terraform/backup-native or cloudformation/backup-native, and keep them for 7 days with none attached. The controller-driven Recipe is backed up through helm/backup-mariadb-operator, the synthesized one by the backup product the Manifest binds; the Compose Recipe has none, so an attachment halts there.
来源
- 内容摘要
- sha256:383ba4f751fe064be0c66c2ad2bc30ea2ff9b75171558aacde8cb5307b4c6d68
- 发布时间
- 2026-11-10T10:10:44Z
- 签名身份
- 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:a0e9576b7851a3aef4c001402e16ca8313944e17607b33ccb645975b2a17cdd4
此版本的引用
oci://hub.aggrega.ai/component/core/datastore/mariadb:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| database | string | — | 是 | Logical database name created on startup. |
| user | string | — | 否 | Application-level database user (non-root). Omit for root-only access. RDS creates only its master user, admin, which the managed Recipes publish as provides.user, so each of them halts the build when this is set. |
| charset | string | utf8mb4 | 否 | Default character set. terraform/mariadb-rds-terraform-aws-modules sets it in the parameter group it creates; the other managed Recipes do not read it, and the instance takes its parameter group's. |
| collation | string | utf8mb4_general_ci | 否 | Default collation. terraform/mariadb-rds-terraform-aws-modules sets it in the parameter group it creates; the other managed Recipes do not read it, and the instance takes its parameter group's. |
| init_scripts | object | — | 否 | SQL scripts executed on first database initialization. Each key is a filename, each value is the SQL content. Scripts run in alphabetical key order. |
| custom_config | string | — | 否 | Raw server configuration block (my.cnf format). Injected verbatim into the server configuration file. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 3306 | 否 | Server listen port. Most operators should omit this and let the Recipe assign the default (3306). |
| engine_version | string | 11.4 | 否 | Server binary version. |
| compute | object | — | 否 | — |
| storage | object | — | 否 | — |
| ha | 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 mariadb-operator control plane is installed in the target cluster. A controller-driven realization halts the build unless this is set true, so a MariaDB custom resource is never emitted as an orphan into a cluster that cannot reconcile it. Every other realization ignores this flag. |
| credentials | string (generated | supplied) | generated | 否 | Who owns the database's credentials on a controller-driven realization. `generated` — the controller creates the credential Secrets and owns both the root password and the application user's, which is what it does when nothing is supplied; the developer's `database` and `user` values are still honored, and no password reaches the rendered artifact. `supplied` — the controller reads both passwords from an existing Secret named in `credentials_secret` and generates neither. Every other realization halts the build on `supplied`: the synthesized ones take the root password from the `root_password` credential slot and the application user's from `user_password`, and on the managed ones RDS owns the password. |
| credentials_secret | string | 否 | Name of the existing Secret a controller-driven realization reads the database credentials from when `credentials` is `supplied`. The Secret lives in the same namespace as the database and carries two entries: `root-password` for the root account and `password` for the application user. Leave it empty when `credentials` is `generated`; a controller-driven build halts if `supplied` is selected without it. Every other realization reads no Secret by this name and halts the build when it is set. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | Address a client opens its database connection to. On the in-cluster realizations it is the Service's DNS name; on a managed one it is a pointer string the provisioning tool resolves to the instance's address once the infrastructure has been applied, or the DNS name the Release sets in infra.overrides.host, so a consumer on another target receives an address it can resolve. |
| port | integer | — | 是 | TCP port the server accepts connections on. It follows the port an operator set, so a consumer reads it rather than assuming 3306. |
| user | string | — | 否 | Name of the login role a consumer authenticates as. The matching password arrives through the credential attached to the component, never through this contract. |
| database | string | — | 否 | Name of the logical database created at startup. A consumer names it in its connection string to land in the right database rather than the server's default. |
| protocol | string | — | 否 | Wire protocol the published address speaks — `mariadb`, which is what a consumer selects a driver for. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| root_password | — | 是 | — | 是 | Root database password. Recipe controls delivery (Black-Box). On helm/mariadb-cluster with infra.credentials generated the controller generates it, so the slot is bound with core/generated-secret, mapped to helm/generated-secret. On the RDS Recipes RDS generates the password of the master user, admin, and keeps it in AWS Secrets Manager, so the slot takes core/generated-secret there, and any other credential halts the build. |
| user_password | — | 否 | env, file | 是 | Application user password. Unattached, helm/mariadb sets it to the development literal `apppass`, which this catalog publishes, so every Release built with that Recipe that leaves the slot unattached shares that password; on helm/mariadb-cluster with infra.credentials generated the controller generates it. The RDS Recipes create only the master user, admin, and halt the build when this slot is filled. |
自注入允许列表
env, file
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
此实体未使用目录中的任何内容。
被使用
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «queue»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «queue»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «queue»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «queue»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «queue»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «state_store»
使用套接字 «checkpointer_db»
使用套接字 «checkpointer_db»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «storage»
使用套接字 «metadata_store»
使用套接字 «target_datastore»
使用套接字 «backend»
使用套接字 «databases»
使用套接字 «etcd»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «state_store»
使用套接字 «forward_target»
使用套接字 «backend»
使用套接字 «cache»
使用套接字 «chunk_cache»
使用套接字 «scrape_target»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «database»
适用于
适用于
适用于
实现
实现
实现
实现
实现
实现
实现