Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

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.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:85ffc765ede3cd63d1f0a5901c86693301410d33d51c6967c3574f7092a2bdca
Dipublikasikan
2026-11-10T10:10:52Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

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

Referensi pada versi ini

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

Parameter pengembang

Nilai yang ditetapkan pengembang di Aggregate.

NamaTipeBawaanWajibDeskripsi
charsetstringutf8mb4tidakDefault character set. Written into the server configuration the custom resource carries.
collationstringutf8mb4_general_citidakDefault collation. Written into the server configuration the custom resource carries.
custom_configstring—tidakRaw server configuration block (my.cnf format). Appended verbatim to the server configuration the custom resource carries.

Penentuan ukuran oleh operator

Ukuran infrastruktur yang disesuaikan operator untuk setiap lingkungan.

NamaTipeBawaanWajibDeskripsi
engine_versionstring8.4.0tidakMySQL 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)1tidakNumber 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)1tidakNumber 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_presentbooleanfalsetidakOperator 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)suppliedtidakWho 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_secretstringtidakName 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.

Kontrak keluaran

Nilai yang dipublikasikan komponen ini kepada konsumen melalui topologi uses.

NamaTipeBawaanWajibDeskripsi
hoststring—yaAddress 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—yaTCP 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—tidakWire protocol the published address speaks — `mysql`, which is what a consumer selects a driver for.

Soket uses

Soket dependensi yang menjadi jalur koneksi komponen ini. Target setiap koneksi yang dihubungkan melalui sebuah soket harus memenuhi selektor labelnya, dan setiap koneksi dapat membawa lampiran pada slot yang dideklarasikan soket tersebut. Slot wajib harus diisi oleh setiap koneksi yang dihubungkan oleh Aggregate atau Release melalui soket tersebut.

Tidak ada soket uses yang dideklarasikan.

Slot lampiran

Titik pengikatan bernama tempat sebuah Feature dilampirkan ke komponen ini. Selektor sebuah slot membatasi Feature mana yang dapat mengisinya, dan daftar injeksinya menyebutkan cara materi Feature dapat dikirimkan. Slot wajib harus terikat pada setiap instans, melalui lampiran pada instans tersebut atau pada cakupan di atasnya, dan slot sensitif dideklarasikan untuk menangani materi rahasia. Sebuah Feature juga dapat dilampirkan dengan nama yang tidak dideklarasikan oleh slot mana pun.

SlotSelektorWajibInjeksiSensitifDeskripsi
root_password—tidak—yaRoot account password. Read when `infra.credentials` is `generated`, to fill the Secret the custom resource names. Leave it unattached when the Secret is supplied.

Daftar izin injeksi mandiri

env, file

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Entitas ini tidak menggunakan apa pun di katalog.

Digunakan oleh

Referensi konsep Component →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi