kubeblocks-engine-postgresql

To deploy a highly available PostgreSQL cluster on Kubernetes, use KubeBlocks to provision the cluster with a defined replication topology, proper serviceVersion, and storage sizing. It guides topology selection and sizing during cluster bootstrap.

KubeBlocks supports two PostgreSQL high availability topologies using Patroni: standard replication and replication-with-etcd. You select the appropriate topology during the create-time bootstrap workflow based on your availability requirements.

Yes, you must run preflight validation checks before provisioning a PostgreSQL cluster on KubeBlocks when your environment readiness is unknown. This ensures your Kubernetes environment meets the requirements for a predictable deployment.

KubeBlocks provides version strategy and storage sizing guidance during the create-time workflow. This ensures your PostgreSQL deployment is configured with the correct serviceVersion and storage capacity before accepting connections.

Yes, the KubeBlocks PostgreSQL provisioning skill applies specifically to create-time bootstrap and first-time deployments. It enforces topology selection, version strategy, and connection methods for initial cluster setup across replication scenarios.

Provisioning PostgreSQL with KubeBlocks is limited to create-time bootstrap and first-time deployments across replication and replication-with-etcd scenarios. It does not handle ongoing cluster modifications or post-deployment scaling operations.