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
• Foundation for Edka MySQL database and MySQL app workflows
• Support for replicated topologies and managed service endpoints
• Backup and restore-oriented runtime wiring used by Edka MySQL flows

How it fits in Edka

Edka installs MOCO when a cluster needs the supported MySQL runtime stack. In practice, you will most often consume it through the Databases workspace or through app flows that depend on MySQL, rather than operating the controller on its own first.

Related docs

• Dedicated Databases Workspace
• MySQL on Edka with MOCO

Open Databases