Cloud Native PostGres (CNPG)¶
Overview¶
CloudNativePG is a Kubernetes-native PostgreSQL operator that enables robust and production-grade PostgreSQL database management. It simplifies the deployment and lifecycle management of PostgreSQL clusters using native Kubernetes resources.
In KubeDNA, CloudNativePG is the default component for PostgreSQL workloads — allowing users to run stateful database services inside their Kubernetes environment in a secure, scalable, and cloud-agnostic way.
✅ Current Implementation¶
In the current version of KubeDNA, users can install CloudNativePG via the Operator, which lays the foundation for managing PostgreSQL clusters.
Installation Path:
[Selected Cluster] > Components > CNPG
- Deploys the CloudNativePG Operator only (no database clusters by default).
- Users can manually define PostgreSQL clusters using Kubernetes CRDs (
Cluster
,Backup
, etc.). - Ideal for teams comfortable writing manifest files or using GitOps pipelines to define databases.
🔜 Upcoming Release – Full HA PostgreSQL Support¶
In the upcoming release, KubeDNA will introduce full High Availability (HA) PostgreSQL support powered by CloudNativePG, with a user-friendly rollout interface.
🚀 Key Features:¶
- HA PostgreSQL Clusters:
- Multi-node PostgreSQL clusters with automated failover
- Built-in replication using native streaming
- PodDisruptionBudget and anti-affinity configured for resilience
- One-Click Database Provisioning:
- Easily deploy and manage PostgreSQL clusters via the KubeDNA UI
- Choose storage classes, replica counts, backup schedules
- Integrated Backup & Restore:
- Scheduled backups with support for object storage (e.g., S3, MinIO)
- Point-in-time recovery (PITR) capabilities
- Monitoring & Observability:
- Integration with OpenTelemetry and Prometheus for performance metrics
- Ready-to-use Grafana dashboards in the platform
- Multi-Tenant Ready:
- Support for namespace-level isolation of databases
- Optional integration with Vault or KubeDNA secrets for secure credential management
🎯 Use Cases¶
- Deploying internal application databases
- Self-hosting PostgreSQL for SaaS workloads
- Staging or test environments with real-time scaling
- Running data services in sovereign cloud or on-prem setups
📌 Notes¶
- The CloudNativePG operator will continue to be available for advanced use cases.
- Users can still use GitOps pipelines to define database clusters declaratively.
- Future releases will support database cloning, scheduled failover, and managed upgrades.