MYSQL // DATABASES
MySQL on Your Cluster
Provision MySQL on your own cluster with the MOCO operator. Configure resources, users, and TLS, schedule backups to S3-compatible storage, and restore snapshots or confirmed archived times.
Powered by MOCO
Available versions
FEATURES // MYSQL
MySQL, the Edka Way
Edka provisions MySQL on your own cluster and gives you a clean control surface for day-2 operations. The data stays in your cloud account.
Topology & Storage
Run replicated MySQL sized to fit.
- 1, 3, or 5 instances
- Expandable storage and per-instance CPU and memory settings
- Node-pool placement and replica spreading
- Runtime version selection (8.0 / 8.4)
Credentials
Manage application access and rotate credentials.
- Managed databases, users, and database grants
- Optional custom admin and writable passwords
- Auto-provisioned connection details
Connectivity
Expose MySQL when you need to reach it.
- Public LoadBalancer, private MetalLB, or Tailscale
- Managed TLS required for public application access
- In-cluster service for app workloads
Maintenance and Insights
Evolve the runtime from one Settings surface.
- Update version, replica count, and storage size
- Planned switchover and rolling restart
- Runtime, connection, and replication metrics
Backups and Recovery
Keep snapshots and binary-log archives in your bucket.
- Scheduled and manual backups run inside your cluster
- Amazon S3 and S3-compatible storage
- Restore snapshots or confirmed archived times into a new installation
Other engines
PostgreSQL 
ClickHouse 
Valkey GET STARTED // NOW
Provision MySQL
Spin up a replicated MySQL runtime with the MOCO operator — on your own infrastructure.
Which MySQL versions can I deploy with Edka?
Available versions today: 8.4.8.1, 8.4.3, 8.0.40. You pick the version when provisioning the runtime.
Can I run replicated MySQL on my own cluster?
Yes. The MOCO operator runs MySQL 8.0 or 8.4 with 1, 3, or 5 instances. Version, replica count, and storage size stay editable from the Settings surface.
How do apps connect to MySQL?
Use the connection details in Overview for in-cluster, public LoadBalancer, private MetalLB, or Tailscale access. Public access requires managed TLS for provisioned application users.
Does MySQL support backups and point-in-time recovery?
Yes. Scheduled and manual backups write snapshots and binary-log archives to Amazon S3 or S3-compatible storage. Binary logs are archived during backup runs, not continuously. Restore creates a new installation from a snapshot or a time within its confirmed archive interval.
Where does my MySQL data live?
In your own Kubernetes cluster, on your own infrastructure. There is no hosted database service in between. You keep full control of the runtime and its storage.