postgresql-health-check

To check Patroni PostgreSQL cluster health in Kubernetes, you can run a health-check workflow that evaluates cluster status, replication, pod resources, PVCs, and disk usage. It executes kubectl commands, Patroni tools, and SQL queries to provide a structured health summary.

A Patroni PostgreSQL health check includes verifying cluster state and history, pod and PVC health, disk usage, resource utilization, and SQL-based health indicators. It uses health_check.sql and replication.sql to evaluate key database metrics across all Patroni pods.

Yes, you can diagnose PostgreSQL replication issues by executing kubectl commands and Patroni tools alongside SQL replication queries. This process evaluates replication status across Patroni pods to identify failures and provide actionable remediation guidance.

You monitor PVC and disk usage for PostgreSQL pods by running a health assessment that checks PVC status and resource utilization across all Patroni pods. The evaluation applies actionable thresholds to identify capacity limits and prevent disk exhaustion.

Yes, you need a running Kubernetes cluster hosting a Patroni-based PostgreSQL deployment. The health check applies specifically to Kubernetes environments running Patroni to evaluate cluster status, replication, and pod resources accurately.

Patroni PostgreSQL cluster replication failures in Kubernetes can stem from pod resource exhaustion, PVC issues, or disk limits. Running a health check executes SQL replication queries and evaluates pod resources to identify the root cause and recommend remediation.