skills.rest
apecloud
apecloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kubeblocks-addon-postgresql

Deploy PostgreSQL clusters on KubeBlocks using Helm and kubectl commands.

3|Updated Mar 12, 2026
Search Tags:#postgresql#helm#kubectl#patroni#kubeblocks#spilo
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-postgresql
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubeblocks-addon-postgresql
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-addon-postgresql
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-postgresql

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy compatibility shim to deploy PostgreSQL on KubeBlocks while preserving the main workflow reference to kubeblocks-engine-postgresql. It ensures older references can still provision and manage PostgreSQL clusters using the legacy path, but should not be used as the primary path for cold-start agents.

Core Features & Use Cases

  • Preserves legacy workflow for PostgreSQL provisioning with Patroni/Spilo-based HA in KubeBlocks.
  • Includes steps for addon installation checks, namespace creation, cluster provisioning, connection, backups, and day-2 operations.
  • Used when referencing the legacy entry while migrating toward the primary engine entry; provides reference workflows and troubleshooting as needed.

Quick Start

Follow the legacy workflow to deploy a PostgreSQL cluster using the addon and reference the primary entry kubeblocks-engine-postgresql for the recommended path.

Frequently Asked Questions about kubeblocks-addon-postgresql

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

FAQPage Schema
How do I deploy PostgreSQL on KubeBlocks using the legacy addon path?▼

To deploy PostgreSQL on KubeBlocks via the legacy path, use Helm and kubectl to check addon installation, create namespaces, provision clusters, and execute day-2 operations using predefined service versions.

When should I use the legacy PostgreSQL path instead of the primary KubeBlocks engine?▼

Use the legacy PostgreSQL path when you need to preserve older references while migrating to the primary kubeblocks-engine-postgresql entry; avoid it for cold-start agent deployments.

Does the KubeBlocks PostgreSQL legacy addon support high availability?▼

Yes, the KubeBlocks PostgreSQL legacy addon supports high availability through Patroni and Spilo integration, maintaining runtime compatibility for cluster provisioning under the legacy shim pathway.

What day-2 operations are available for PostgreSQL clusters on KubeBlocks?▼

Day-2 operations for PostgreSQL clusters on KubeBlocks include connection management, backups, and troubleshooting workflows, all executed via kubectl within the legacy addon reference.

Why is my KubeBlocks PostgreSQL legacy path not working for new deployments?▼

The KubeBlocks PostgreSQL legacy path may fail for new deployments because it is a compatibility shim designed for older references, not a primary path for cold-start agent provisioning.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-manage-addons

Manage KubeBlocks addons to install, upgrade, and configure database engines.

Official
Intermediate
apecloudapecloud
3

kubeblocks-addon-rabbitmq

Provides legacy RabbitMQ provisioning compatibility shim for KubeBlocks.

Official
Basic
IldarMinaevIldarMinaev
1

postgresql-health-check

Evaluate Patroni-managed PostgreSQL cluster health on Kubernetes.

Community
Advanced
apecloudapecloud
3

kubeblocks-addon-kafka

Route legacy Kafka provisioning requests to kubeblocks-engine-kafka.

Official
Intermediate