Component
core/datastore/mysql-innodb-cluster
A MySQL InnoDB Cluster, realized as an InnoDBCluster custom resource the MySQL Operator for Kubernetes reconciles. The emitted custom resource requests a count of MySQL server instances and a count of MySQL Router instances, and the controller acts on that request inside the target cluster — so what this component describes is what is asked for, never what ends up running. What it publishes is root access at an in-cluster address: the controller establishes the root account from the Secret the custom resource names, and creates neither a logical database nor an application user, so this component declares neither and whoever holds root creates the schemas and accounts an application needs. Reach for core/datastore/mysql where the application wants a logical database and a login role created for it, and where nothing may need installing first — its synthesized Recipe needs no controller and no chart repository, so it builds with nothing fetched. Reach for this component where the MySQL Operator control plane is already installed in the target cluster, which core/datastore/mysql-operator declares and installs.
来源
- 内容摘要
- sha256:85ffc765ede3cd63d1f0a5901c86693301410d33d51c6967c3574f7092a2bdca
- 发布时间
- 2026-11-10T10:10:52Z
- 签名身份
- 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:0f1da829095d0aad0c4c536b78c703b16cf839fffc27fa011e6b3b5c71609f65
此版本的引用
oci://hub.aggrega.ai/component/core/datastore/mysql-innodb-cluster:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| charset | string | utf8mb4 | 否 | Default character set. Written into the server configuration the custom resource carries. |
| collation | string | utf8mb4_general_ci | 否 | Default collation. Written into the server configuration the custom resource carries. |
| custom_config | string | — | 否 | Raw server configuration block (my.cnf format). Appended verbatim to the server configuration the custom resource carries. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| engine_version | string | 8.4.0 | 否 | MySQL Server version the custom resource requests. The custom resource accepts a three-part version — major, minor and patch, optionally followed by a suffix — so a two-part value renders and is then rejected when the resource is applied. A build halts on a value the custom resource would reject. |
| server_instances | integer (min 1, max 9) | 1 | 否 | Number of MySQL server instances the custom resource requests. One is the custom resource's own default and nine is the highest it accepts. |
| router_instances | integer (min 1) | 1 | 否 | Number of MySQL Router instances the custom resource requests. One is the custom resource's own default. The published address is the Service the routers answer on, so this component does not offer a request of zero: an address nothing answers on would render as cleanly as one that works. |
| control_plane_present | boolean | false | 否 | Operator affirmation that the MySQL Operator control plane is installed in the target cluster. The build halts unless this is set true, so an InnoDBCluster custom resource is never emitted as an orphan into a cluster that cannot reconcile it. |
| credentials | string (generated | supplied) | supplied | 否 | Who owns the Secret holding the cluster's root account — the Secret the custom resource names and the controller reads. `supplied` — the Secret already exists in the target cluster and is named in `credentials_secret`; nothing is rendered for it and no password reaches the rendered artifact. `generated` — the Secret is rendered beside the custom resource from the credential attached to the `root_password` slot, so the password is carried in the rendered output. `supplied` is the default because the controller establishes the root account from a Secret it is pointed at and creates none of its own. |
| credentials_secret | string | 否 | Name of the existing Secret the controller reads the root account from when `credentials` is `supplied`. The Secret lives in the same namespace as the cluster and carries the account's user name, host and password under the keys `rootUser`, `rootHost` and `rootPassword`. Leave it empty when `credentials` is `generated`; a build halts if `supplied` is selected without it. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | Address a client opens its database connection to. The controller creates a Service under the custom resource's own name, and that bare in-cluster name is what is published; a consumer in another namespace qualifies it with that namespace on its own side. |
| port | integer | — | 是 | TCP port the published address accepts connections on. The custom resource carries no field that moves it, so it is the port the controller publishes by default. |
| protocol | string | — | 否 | Wire protocol the published address speaks — `mysql`, which is what a consumer selects a driver for. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| root_password | — | 否 | — | 是 | Root account password. Read when `infra.credentials` is `generated`, to fill the Secret the custom resource names. Leave it unattached when the Secret is supplied. |
自注入允许列表
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»
适用于
适用于
适用于
实现