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.
Herkunft
- Inhalts-Digest
- sha256:85ffc765ede3cd63d1f0a5901c86693301410d33d51c6967c3574f7092a2bdca
- Veröffentlicht
- 2026-11-10T10:10:52Z
- Signaturidentität
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signatur
- Offiziellapplication/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
Referenz zu dieser Version
oci://hub.aggrega.ai/component/core/datastore/mysql-innodb-cluster:1.0.0Entwicklerparameter
Werte, die der Entwickler im Aggregate festlegt.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| charset | string | utf8mb4 | nein | Default character set. Written into the server configuration the custom resource carries. |
| collation | string | utf8mb4_general_ci | nein | Default collation. Written into the server configuration the custom resource carries. |
| custom_config | string | — | nein | Raw server configuration block (my.cnf format). Appended verbatim to the server configuration the custom resource carries. |
Dimensionierung durch den Operator
Infrastrukturdimensionierung, die der Operator pro Umgebung anpasst.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| engine_version | string | 8.4.0 | nein | 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 | nein | 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 | nein | 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 | nein | 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 | nein | 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 | nein | 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. |
Ausgabevertrag
Werte, die diese Komponente über die uses-Topologie an Konsumenten veröffentlicht.
| Name | Typ | Standardwert | Erforderlich | Beschreibung |
|---|---|---|---|---|
| host | string | — | ja | 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 | — | ja | 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 | — | nein | Wire protocol the published address speaks — `mysql`, which is what a consumer selects a driver for. |
uses-Sockets
Die Abhängigkeits-Sockets, über die sich diese Komponente verbindet. Das Ziel jeder über einen Socket verdrahteten Verbindung muss dessen Label-Selektor erfüllen, und jede Verbindung kann in den Slots, die der Socket deklariert, eine Anbindung tragen. Einen erforderlichen Slot muss jede Verbindung füllen, die das Aggregate oder das Release über den Socket verdrahtet.
Keine uses-Sockets deklariert.
Anbindungs-Slots
Benannte Bindungspunkte, an denen ein Feature an diese Komponente angebunden wird. Der Selektor eines Slots schränkt ein, welches Feature ihn füllen darf, und seine inject-Liste benennt, wie das Feature sein Material liefern darf. Ein erforderlicher Slot muss auf jeder Instanz gebunden sein, durch eine Anbindung an der Instanz oder in einem darüberliegenden Geltungsbereich, und ein sensibler Slot ist für den Umgang mit geheimem Material deklariert. Ein Feature kann auch unter einem Namen angebunden werden, den kein Slot deklariert.
| Slot | Selektor | Erforderlich | Injektion | Sensibel | Beschreibung |
|---|---|---|---|---|---|
| root_password | — | nein | — | ja | 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. |
Zulassungsliste für Selbstinjektion
env, file
Beziehungen
Typisierte Kanten zu und von anderen veröffentlichten Entitäten. Eine Referenz ohne veröffentlichtes Ziel wird als unterbrochene Kante statt als Link dargestellt.
Verwendet
Diese Entität verwendet nichts aus dem Katalog.
Verwendet von
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «queue»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «queue»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «queue»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «queue»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «queue»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «state_store»
verwendet Socket «checkpointer_db»
verwendet Socket «checkpointer_db»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «storage»
verwendet Socket «metadata_store»
verwendet Socket «target_datastore»
verwendet Socket «backend»
verwendet Socket «databases»
verwendet Socket «etcd»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «state_store»
verwendet Socket «forward_target»
verwendet Socket «backend»
verwendet Socket «cache»
verwendet Socket «chunk_cache»
verwendet Socket «scrape_target»
verwendet Socket «backend»
verwendet Socket «backend»
verwendet Socket «database»
gilt für
gilt für
gilt für
implementiert