CloudNativePG is a full lifecycle Kubernetes operator of a highly available PostgreSQL cluster. Use this tag for questions regarding the operator, cluster configuration or issues with backups replication, etc. It should not be used for general PostgreSQL cluster questions. Questions should include relevant Cluster configuration, minimal cluster or operator logs, just enough to give an idea of what you are trying to achieve and where it's failing.
CloudNativePG is the Kubernetes operator that covers the full lifecycle of a highly available PostgreSQL database cluster with a primary/standby architecture, using native streaming replication.
CloudNativePG automates the steps that a human operator would do to deploy and to manage a Postgres database inside Kubernetes, including automated failover.
It doesn’t rely on statefulsets and uses its own way to manage persistent volume claims where the PGDATA is stored.
It’s entirely declarative, and directly integrates with the Kubernetes API server to update the state of the cluster — for this reason, it does not require an external failover management tool.
Documentation
Full documentation for each operator version can be found here.
Issues
For any technical issues, feature requests or operation contrary to its documentation you can create an issue in the CloudnativePG GitHub repository.
