Percona Operator vs. Red Hat Advanced Cluster Management for Kubernetes

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

Well suited for - Large-scale Edge deployments of OpenShift instances. Policy-based consistency for all workloads is Less appropriate for - Small-scale deployments. Stand-alone deployments of K8s clusters. Deployments in the same data center.

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• Continuous deployment of other OpenShift instances.
• Controls clusters and applications from a single console.
• Built-in Security & compliance.

• Some differences compared to "traditional" MySQL solution.
• Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc.
• The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor.

• Initial deployment of the ACM itself needs to be made easy.
• Dependency on the Software versions of underlying open shift workloads during upgrades.
• LCM of ACM itself.

Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.

Well documented, there was no need to contact support.

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.

I have also used TNA by Google Cloud, but that is not mature enough as ACM. Right now, ACM is the best choice as a cluster manager for private cloud data centers.

• It allowed us to use k8s on our entire infrastructure.
• Decreased administrative overhead around our db services.
• As it is an open source technology, it cut down our db pricings.

• Reduced the deployment duration of individual nodes by 50%.
• Acts as a central manager for all the clusters.
• Provides a lot of infrastructure options (storage, networking, etc) to build instances of your choice.