kubeblocks-engine-postgresql

Name: kubeblocks-engine-postgresql
Availability: InStock
Author: ApeCloud

Provision PostgreSQL clusters on KubeBlocks with topology, version, storage, and sizing.

3|Updated Mar 12, 2026

Search Tags:#database #postgresql #topology #cluster #ha #patroni #kubeblocks

Ready to run

npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-postgresql

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kubeblocks-engine-postgresql
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-engine-postgresql
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-engine-postgresql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a primary create-time entry to provision PostgreSQL on KubeBlocks, guiding topology, version, storage, sizing, and connections, with preflight checks when environment readiness is unknown.

Core Features & Use Cases

Centralized create-time workflow for PostgreSQL on KubeBlocks with sensible defaults and topology options (replication, replication-with-etcd).
Guidance on version strategy, storage sizing, and preflight requirements, enabling predictable deployments in cluster bootstrap scenarios.
Use Case: An operator needs to deploy a highly available PostgreSQL cluster with a defined topology and proper serviceVersion, ready to accept connections.

Quick Start

Create a new PostgreSQL cluster using the primary create path, ensuring preflight is run if environment is not profiled.

Frequently Asked Questions about kubeblocks-engine-postgresql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy a highly available PostgreSQL cluster on Kubernetes?▼

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.

What PostgreSQL high availability topologies can I configure with Patroni on KubeBlocks?▼

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.

Do I need to run preflight checks before provisioning a PostgreSQL cluster on KubeBlocks?▼

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.

How do I choose the right PostgreSQL version and storage sizing for a KubeBlocks 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.

Can I provision a PostgreSQL cluster on KubeBlocks for first-time deployments only?▼

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.

What are the limitations of provisioning PostgreSQL with KubeBlocks?▼

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.