Cloud Native Data on K8s: The Good, Bad, and the Unknown
summary
Covers history, tools, and hands‑on deployments: deploys Postgres as a statefulset (shows Helm to avoid raw yamls), compares using the CSI for storage, cloud options like MongoDB Atlas and Amazon RDS, and operator-based control with CloudNative Postgres and Crunchy operators. Claims operators give reconciliation and self‑healing but add CPU/memory overhead and custom‑code risk. Emphasizes backups still required — high availability is not backup — and cites a 25k‑star GitHub learning repo and a donated canister blueprint for protection.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:27Defining cloud-native data
- 5:25Cloud-native vs traditional
- 7:56Strategic deployment options
- 10:41Choosing the right architecture
- 12:55Stateful sets and management
- 15:47The role of Kubernetes operators
- 18:31Managed platform services
- 20:41Conclusion and resources
related talks
28mLightning Talk: Cloud Native PostgreSQL - Running PostgreSQL on Kubernetes
30mBridging the DevOps to Data Divide with a Common Cloud Native Stack
48mPostgres and Kubernetes: Past, Present and Future
50mDemystifying Kubernetes for Postgres DBAs; A Guide to Operators
28mCloud Native Tech: The Building Blocks of Modern DB Software
54mPostgres: From Cloud to Hybrid and On Prem Again
26mBeyond the DBaaS Trap: Achieving Data Sovereignty With Kubernetes and CloudnativePG
41mCloud-Native Databases in Kubernetes with OpenShift and Postgres