MOCO

MOCO is the MySQL operator Edka uses for Kubernetes native MySQL runtimes. It provides the control plane for MySQL clustering, failover, and service endpoints inside the cluster.

Features available

• Operator-managed MySQL clusters on Kubernetes
• Powers the managed MySQL engine in the Databases workspace
• Support for replicated topologies and managed service endpoints
• Native snapshot backups and binary-log recovery, orchestrated by Edka

How it fits in Edka

Edka installs MOCO when a cluster needs the supported MySQL runtime stack. In practice, create and operate MySQL through Clusters → Databases. Edka adds resource controls, managed users, TLS, scheduled S3-compatible backups, restore, and maintenance actions around the operator.

Related docs

• MySQL setup and operations
• Dedicated Databases Workspace
• MySQL on Edka with MOCO

Open Databases