Simon R.
"Postgres for Kubernetes - an efficient way of operating DBs"
What do you like best about EDB Cloud Native PostgreSQL?
We do not need to setup another VM for each Workload requiring a Relational DB. Setting up a EDB CNP is really easy now. Just by the input of some basic properties the operator spins up a Postgres Cluster on it's own and in combination with the ClusterImageCatalog patching the Clusters is very easy since the operator is conducting a rolling restart of the pods on its own on updating the Catalog. We also like the many options the Operator already provides in configuring the Postgres Cluster.
Cudos also to the Operator which has become much more stable since we started initially ~2 years ago. Review collected by and hosted on G2.com.
What do you dislike about EDB Cloud Native PostgreSQL?
We are still missing major upgrades on the Clusters in a user friendly way. I know there is progress on EDB's Development making customers life more easy, but we are still eagerly awating it. The current solution based on replicating data to a new cluster with a higher major version is far to complicated and time consuming for a bunch of Clusters.
Besides we are missing the ClusterImageCatalog formerly provided here https://raw.githubusercontent.com/EnterpriseDB/docker-postgresql/refs/heads/main/image-catalogs/ClusterImageCatalog-ubi9.yaml
It was very handy to pull this Catalog and apply it to the Cluster using Terraform and with that triggering the operator to patch all Clusters. Review collected by and hosted on G2.com.
Validated through a business email account
This reviewer was offered a nominal incentive as thanks for completing this review.
Invitation from G2 on behalf of a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review.