Anyone who has ever built a DIY database setup on Kubernetes knows the pain 🤦‍♂️. Yes, operators from Zalando, CNPG, StackGres, Percona and others have already made life much easier - but you still end up stitching different APIs, UIs, CRDs and workflows together depending on which engine you run.

Percona decided to take this one level further with OpenEverest.

Think of it as “one operator to rule them all” 👑 - not by replacing existing operators, but by orchestrating them. Under the hood, OpenEverest leverages Kubernetes operators for MySQL, PostgreSQL and MongoDB, while exposing a unified API and a single pane of glass to manage all three. Same lifecycle concepts, same workflows, same UX - regardless of the engine.

From a platform perspective, this is the interesting part: databases stop being special snowflakes and start looking like standardized platform resources. Provisioning, horizontal and vertical scaling, storage classes, backups, restores, access configuration - all become declarative, Kubernetes-native and versioned. Add namespace-level isolation, PMM-based monitoring and both UI + API access and you get something that feels very close to a portable, private DBaaS.

Philosophically OpenEverest is also clearly aiming to avoid vendor lock-in: run it on any Kubernetes - on-prem or cloud and keep control of your data plane and your ops model.

Will it become a serious competitor to KubeBlocks? Very likely. KubeBlocks goes wider in terms of supported engines today, OpenEverest goes harder on unification and operational consistency. Different trade-offs, same direction: making “databases on Kubernetes” less of a dark art and more of a boring, repeatable platform capability.

And this is only the beginning. The OpenEverest team is turning it into a modular core 📦, where databases, storage and other technologies become plugins. ClickHouse, Vitess, DocumentDB, Valkey and deeper integrations with Prometheus and the rest of the ecosystem are already on the roadmap.

Even more importantly, the project is committed to staying truly open 🤗: the plan is to donate OpenEverest to the CNCF and guide it through incubation, ensuring open governance, vendor neutrality and long-term community ownership.

If that vision lands, OpenEverest won’t just be “another DB platform on Kubernetes” - it’ll be a foundation for building open, portable, cloud-native data platforms.

2026-02-07 12:56:35 +0400 +0400 - Radagast the Brown