KubeBlocks for
MySQL
MySQL is the world's most popular open-source relational database, trusted by millions of applications for its reliability, performance, and ease of use. It powers everything from web applications and e-commerce platforms to enterprise data warehouses.
Supported versions
Available on
AWS
Azure
GCP
OCI
Alibaba Cloud
Rancher
OpenShiftDatabases
MySQL
PostgreSQLOracle
SQL Server
Redis
MongoDB
ClickHouseVector & AI
Qdrant
Milvus
ElasticsearchMessage queues
RocketMQ
RabbitMQ
KafkaOthers
VictoriaMetrics
InfluxDB
etcdExtend database engines like plug-ins
KubeBlocks provides unified database operations through its addon-based architecture. With KubeBlocks Enterprise, access over 15 seamless integrations to scale your database services.
One control plane, consistent operations across all engines — powered by the addon mechanism.
Real MySQL capabilities, grouped by functional category
The MySQL addon page should explain capabilities the same way users encounter them in the product: by category. The sections below map to lifecycle, scale, switchover, parameter, accessibility, data management, observability, audit, and backup workflows.
Lifecycle
Manage cluster creation and service state transitions
Users can provision a replicated MySQL cluster, review version and topology details, and drive restart or state transitions from the same guided console workflow.
- Create MySQL 5.7, 8.0, or 8.4 clusters with replication topology and curated sizing defaults.
- Run restart, stop, and start operations without switching tools or losing cluster context.
- Keep lifecycle progress visible with task and status feedback on the cluster detail page.
Creation lands users on a cluster overview with topology, sizing, version, and lifecycle controls.
Restart workflows stay visible in context so users can follow rolling changes without guessing cluster state.
Scale
Scale compute, replicas, and storage by category
Scaling capabilities are grouped around the exact MySQL resources users need to adjust: CPU and memory, replica count, and storage volume size.
- Use vertical scaling to increase CPU and memory for heavier transactional workloads.
- Use horizontal scaling to add replicas for read capacity and topology resilience.
- Expand storage online as data volume grows, without rebuilding the cluster footprint.
Vertical scaling exposes resource changes as a guided task instead of a manual configuration exercise.
Volume expansion keeps persistent storage growth inside the same operational workflow.
SwitchOver
Execute planned primary-secondary role changes with topology in view
SwitchOver is presented as its own capability so users can perform planned role transitions with clear visibility into the resulting primary and replica layout.
- Select the target replica directly from the cluster topology context.
- Verify which node becomes the new primary immediately after the operation.
- Keep planned failover separate from scaling and lifecycle workflows.
Switchover keeps the new primary and remaining replicas visible on the same topology view.
Parameter
Adjust runtime parameters through a dedicated configuration flow
Parameter changes are grouped independently from lifecycle and scaling so users can review value changes and apply runtime tuning with less ambiguity.
- Edit engine parameters such as `max_connections` from the parameters page.
- Review the before-and-after value change in a configuration-focused workflow.
- Keep parameter tuning conceptually separate from resource scaling and failover actions.
Parameter reconfiguration is framed as its own operation category instead of being mixed into general operations.
Accessibility
Control network exposure with explicit IP whitelist rules
Accessibility settings are shown as a separate category so users can understand that connection policy, not data management, governs who may reach the database.
- Define CIDR-based whitelist groups for inbound database access.
- Review default and custom rules side by side from the access rules page.
- Keep network access policy distinct from account, schema, and query workflows.
IP whitelist management gives users a dedicated place to control which clients can connect.
Data Management
Create databases, accounts, and SQL workflows for application teams
Data Management gathers schema and account tasks into one category, giving users a cleaner path from database creation to SQL validation.
- Create databases for isolated workloads directly from the databases page.
- Create accounts and assign least-privilege access for application usage.
- Use SQL Workbench to validate schema creation, inserts, and query results.
Account creation and permission assignment stay inside a dedicated data management workflow.
SQL Workbench lets users verify real read and write behavior without leaving the console.
Observability
Monitor metrics and logs from MySQL-specific runtime views
Observability is grouped around runtime insight: health dashboards, connection trends, throughput metrics, and log inspection for troubleshooting.
- Track uptime, QPS, connections, and InnoDB behavior from metrics dashboards.
- Inspect runtime logs, slow query logs, and HA-related log streams.
- Keep operational visibility separate from audit and backup workflows.
Metrics dashboards expose live throughput, uptime, connections, and buffer usage for each instance.
Logs views let users inspect runtime and slow query output from the same MySQL workspace.
Audit
Review SQL history and task records as audit evidence
Audit capabilities are grouped separately from observability so users can distinguish runtime monitoring from change traceability and SQL accountability.
- Review executed SQL statements and their source account from SQL Audit.
- Track restart, scaling, restore, and other operational tasks from the task list.
- Use audit pages to understand who changed what and when.
SQL Audit provides a dedicated history of executed statements rather than mixing them into logs.
Task history records the operational timeline for lifecycle, scaling, and recovery workflows.
Backup
Protect and recover data with backup and restore workflows
Backup capabilities are kept in their own category so users can understand policy, execution, and recovery as data protection workflows rather than generic operations.
- Trigger full or on-demand backups and review repository, retention, and policy status.
- Track backup task progress from running to completed on the backups page.
- Restore into a new cluster when validation or recovery requires an isolated target.
Backup views combine policy, repository, schedule, retention, and job status in one page.
Restore workflows create a dedicated recovery path that stays distinct from routine operations.
Ready to build your own DBaaS on Kubernetes?
Talk to our team and see how KubeBlocks Enterprise can help you consolidate databases, strengthen security, and reduce operational costs.