Bringing Databases and Kubernetes Together

Why It Matters

OpenEverest gives enterprises a way to automate database operations on Kubernetes without tying them to a single cloud provider, accelerating platform‑engineering initiatives and reducing long‑term cost and lock‑in risk.

Key Takeaways

• 45% of container users run databases, per Datadog survey
• 75% of data workloads now live in containers for advanced teams
• Operators automate backups but still need expert configuration
• OpenEverest offers vendor‑neutral DBaaS on Kubernetes, reducing lock‑in

Pulse Analysis

Kubernetes has become the de‑facto environment for modern cloud‑native workloads, and databases are now its most popular use case. Recent surveys show nearly half of organizations that containerize applications also containerize their databases, while leading teams have shifted three‑quarters of data workloads onto Kubernetes clusters. This shift was made possible by core platform enhancements such as StatefulSets, PersistentVolumes, and a decade of Operator development that translate traditional stateful services into declarative, self‑healing pods.

Despite the progress, Day 2 operational challenges persist. Backup scheduling, high‑availability failover, security hardening, and disaster recovery demand more than the basic restart logic Kubernetes provides for stateless apps. As a result, many developers gravitate toward managed DBaaS offerings, which grew at roughly twice the rate of on‑premises deployments last year. While DBaaS simplifies operations, it also locks customers into a single provider’s APIs and pricing model, limiting portability and increasing long‑term expenses for organizations that value multi‑cloud flexibility.

OpenEverest, the open‑source successor to Percona’s Everest project, seeks to bridge that gap. Now a CNCF‑graduated project, OpenEverest bundles community‑maintained Operators for MySQL, PostgreSQL, and MongoDB, delivering automated backup, scaling, and failover capabilities comparable to commercial DBaaS but without vendor lock‑in. By exposing a unified API and encouraging contributions for additional databases, the project empowers internal developer platforms to offer self‑service, cloud‑agnostic database provisioning. As the ecosystem matures, OpenEverest could become the cornerstone for enterprises aiming to combine the agility of Kubernetes with the reliability of traditional database services.