KubeDB provides operators that manage database deployments through Kubernetes resources. A team describes a supported database configuration and the relevant controller handles the associated workload resources, reducing some of the manual work of operating database servers. It is useful when that engine's supported operator model matches the platform. Database versions, licensing, storage and recovery still require explicit choices; an operator installation alone does not validate an application's production database design.
Current guidance
KubeDB is AppsCode’s Kubernetes database-operator family. Current installation documentation supports Helm and several GitOps workflows and includes obtaining a license from the AppsCode license server. The historical phrase production grade does not establish that every engine, topology and feature has the same support or entitlement.
Select the database engine and version first, then check the corresponding operator release, Kubernetes compatibility and required custom resources. Separate the operator’s responsibilities from application schema migrations, database users, storage performance and backup retention. Review current license terms and deployment credentials rather than assuming that an old public chart defines present licensing.
Before adopting or upgrading, rehearse database creation, a pod replacement and restoration into a separate namespace with representative data. Confirm which component performs backups and whether those backups remain usable independently of the original operator installation. Keep operator upgrades and database major-version changes as explicit steps with their own rollback limits. This review examined current installation requirements; it does not certify every KubeDB engine or claim that an untested cluster configuration is production ready.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
KubeDB by AppsCode – Making running production-grade databases easy on Kubernetes. This chart bootstraps a KubeDB controller deployment on a Kubernetes cluster using the Helm package manager.
Running production quality database in Kubernetes can be tricky, to say the least. In the early days of Kubernetes, replication controllers were used to running a single pod for a database. With the introduction of StatefulSet, it became easy to run a Docker container for any database. But what about monitoring, taking periodic backups, restoring from backups or cloning from an existing database? KubeDB is a framework for writing operators for any database that support the following operational requirements:
- Create a database declaratively using CRD.
- Take one-off backups or periodic backups to various cloud stores, eg, S3, GCS, Azure etc.
- Restore from backup or clone any database.
- Native integration with Prometheus for monitoring via CoreOS Prometheus Operator.
- Apply deletion lock to avoid accidental deletion of the database.
- Keep track of deleted databases, cleanup prior snapshots with a single command.
- Use cli to manage databases like kubectl for Kubernetes.
KubeDB is developed at AppsCode to run their SAAS platform on Kubernetes. Currently, KubeDB includes support for following data stores:
- Postgres
- Elasticsearch
- MySQL
- MongoDB
- Redis
- Memcached
Supported Elasticsearch Features
- Clustering
- Authentication (using Search Guard)
- Authorization (using Search Guard)TLS certificates (using Search Guard)
- Persistent Volume
- Instant Backup
- Scheduled Backup
- Initialization from Snapshot
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
- Supported Memcached Features
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
Supported MongoDB Features
- Persistent Volume
- Instant Backup
- Scheduled Backup
- Initialization from Snapshot
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
Supported MySQL Features
- Persistent Volume
- Instant Backup
- Scheduled Backup
- Initialization from Snapshot
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
Supported PostgreSQL Features
- Clustering
- Warm Standby
- Hot Standby
- Streaming Replication
- Automatic Failover
- Continuous Archiving using wal-g
- Initialization from WAL archive
- Persistent Volume
- Instant Backup
- Scheduled Backup
- Initialization from Snapshot
- Initialization using Script
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
Supported Redis Features
- Persistent Volume
- Builtin Prometheus Discovery
- Using CoreOS Prometheus Operator
Sources & further reading
Spotted something that needs another look?
Help improve this page →