Esta página se tradujo automáticamente. Leer el original en inglés.

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.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:85ffc765ede3cd63d1f0a5901c86693301410d33d51c6967c3574f7092a2bdca
Publicado
2026-11-10T10:10:52Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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

Referencia en esta versión

oci://hub.aggrega.ai/component/core/datastore/mysql-innodb-cluster:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
charsetstringutf8mb4noDefault character set. Written into the server configuration the custom resource carries.
collationstringutf8mb4_general_cinoDefault collation. Written into the server configuration the custom resource carries.
custom_configstring—noRaw server configuration block (my.cnf format). Appended verbatim to the server configuration the custom resource carries.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
engine_versionstring8.4.0noMySQL 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_instancesinteger (min 1, max 9)1noNumber of MySQL server instances the custom resource requests. One is the custom resource's own default and nine is the highest it accepts.
router_instancesinteger (min 1)1noNumber 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_presentbooleanfalsenoOperator 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.
credentialsstring (generated | supplied)suppliednoWho 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_secretstringnoName 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.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—sí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.
portinteger—sí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.
protocolstring—noWire protocol the published address speaks — `mysql`, which is what a consumer selects a driver for.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

No se declararon sockets uses.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

SlotSelectorObligatorioInyecciónSensibleDescripción
root_password—no—sí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.

Lista de permitidos de autoinyección

env, file

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Esta entidad no usa nada del catálogo.

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad