Esta página foi traduzida automaticamente. Leia o original em 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.

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:85ffc765ede3cd63d1f0a5901c86693301410d33d51c6967c3574f7092a2bdca
Publicado
2026-11-10T10:10:52Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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

Referência nesta versão

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

Parâmetros do desenvolvedor

Valores que o desenvolvedor define no Aggregate.

NomeTipoPadrãoObrigatórioDescrição
charsetstringutf8mb4nãoDefault character set. Written into the server configuration the custom resource carries.
collationstringutf8mb4_general_cinãoDefault collation. Written into the server configuration the custom resource carries.
custom_configstring—nãoRaw server configuration block (my.cnf format). Appended verbatim to the server configuration the custom resource carries.

Dimensionamento do operador

Dimensionamento de infraestrutura que o operador ajusta por ambiente.

NomeTipoPadrãoObrigatórioDescrição
engine_versionstring8.4.0nãoMySQL 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)1nãoNumber 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)1nãoNumber 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_presentbooleanfalsenãoOperator 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)suppliednãoWho 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_secretstringnãoName 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 saída

Valores que este componente publica para os consumidores pela topologia uses.

NomeTipoPadrãoObrigatórioDescrição
hoststring—simAddress 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—simTCP 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—nãoWire protocol the published address speaks — `mysql`, which is what a consumer selects a driver for.

Sockets uses

Os sockets de dependência pelos quais este componente se conecta. O destino de cada conexão ligada por um socket deve satisfazer o seletor de rótulos dele, e cada conexão pode carregar um acoplamento nos slots que o socket declara. Cada conexão que o Aggregate ou a Release liga pelo socket deve preencher os slots obrigatórios.

Nenhum socket uses declarado.

Slots de acoplamento

Pontos de vinculação nomeados nos quais uma Feature se acopla a este componente. O seletor de um slot restringe qual Feature pode preenchê-lo, e sua lista inject indica como o material da Feature pode ser entregue. Um slot obrigatório deve estar vinculado em cada instância, por um acoplamento na instância ou em um escopo acima dela, e um slot sensível é declarado para lidar com material secreto. Uma Feature também pode se acoplar com um nome que nenhum slot declara.

SlotSeletorObrigatórioInjeçãoSensívelDescrição
root_password—não—simRoot 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 permissões de autoinjeção

env, file

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

Esta entidade não usa nada do catálogo.

Usado por

Referência do conceito Component →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade