USING KUBERNETES/DOCKER/HELM TO DEPLOY ON-DEMAND POSTGRESQL STREAMING REPLICAS
summary
Kubernetes + Docker + Helm deploy on-demand Postgres streaming replicas using StatefulSets, PersistentVolumes (GCE/EBS), and PG_BASEBACKUP; Helm values.yaml drives config and replication setup so a replica spins up in 10–15 seconds in the demo, with WAL sender streaming to read‑only replicas. Production example builds 75 databases, 225 TB into a DR site on the fly. No automatic failover by default (crunchywatch or Patroni handle promotion), services use clusterIP/nodePort, and the container uses a tail hack for live debugging.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:57Kubernetes
- 6:22Databases Perform Better in the Container
- 7:43Demo
- 9:35Kubernetes Setup
- 15:07Auto Scaling Groups
- 18:53Host Based Authentication Rules
- 24:29Automatic Failover
- 27:34Upgrading Postgres Versions
related talks
48mPostgreSQL in Kubernetes: Operation - Day 2
27mFrom Zero to Hero: Scaling Postgres in Kubernetes Using the Power of...
26mKubernetes from the Database Out
35mContainerizing PostgreSQL and Making it Cloud Native Ready
22mSecuring Postgres with streaming replication
36mKube-native Postgres [I]
37mData On Kubernetes, Deploying And Running PostgreSQL And Patterns For Databases In a Kubernetes Cluster.
34mElephants on Automatic: HA Clustered PostgreSQL with Helm [I]