OpenEverest: Open-source Database Management on Kubernetes
Welcome back to your newsletter!
This week we're diving into OpenEverest, an open-source platform for provisioning and managing databases on Kubernetes launched by Percona.
Let`s dive in to see how it might help you!
What is OpenEverest?
Originally launched as Percona Everest, the project is now positioned as a vendor-neutral solution. It can run on any Kubernetes infrastructure, whether in the cloud or on-premises.
The aim is to give teams a private DBaaS experience without being tied to a single cloud provider or proprietary control plane.
Why does it matter?
Database platforms often come with hidden lock-in. OpenEverest is designed to avoid that.
It is built on Kubernetes operators rather than cloud-specific services. This allows platform teams to standardise database operations while keeping flexibility over where and how databases run.
The architecture is modular. Teams can combine different database engines, storage layers, and deployment patterns based on their own requirements.
How it works in practice
OpenEverest focuses on simplifying operational work.
Through a web UI and REST API, teams can manage:
Database lifecycle operations are handled through Kubernetes Custom Resource Definitions such as DatabaseCluster, DatabaseClusterBackup, and DatabaseClusterRestore. This makes databases first-class Kubernetes objects and hides many engine-specific differences.
Database support today
OpenEverest currently supports:
These are managed using Percona’s database operators.
The latest release, v1.11.0, adds support for PostgreSQL 18.1 and more flexible networking via NodePort.
Support for ClickHouse, Vitess, DocumentDB, Valkey, and deeper observability integrations (including Prometheus) is on the roadmap.
Recommended by LinkedIn
Kubernetes and databases: still controversial?
The beta release sparked debate, particularly on Hacker News. Some remain sceptical about running databases on Kubernetes. Others argue this view is outdated.
According to the Data on Kubernetes survey, around 50% of organisations already run data workloads on Kubernetes in production.
For many teams, managed backups, scaling, upgrades, and consistency with the rest of the platform outweigh the risks.
Governance and the bigger picture
A key shift is governance. OpenEverest is transitioning to an independent open-source project with open, community-driven governance.
The team plans to donate the project to the Cloud Native Computing Foundation, aiming for long-term neutrality and multi-vendor participation.
OpenEverest enters a competitive space alongside tools like KubeBlocks and database-specific operators such as StackGres. Its differentiators are openness, Apache 2.0 licensing, and a clear focus on avoiding vendor lock-in.
For teams already standardising on Kubernetes, OpenEverest is one to keep an eye on.
Kubernetes for databases is still controversial, but the direction is clear. Teams want the same operational model everywhere, including data.