Cross-Cloud Migrations With Databases on Kubernetes
summary
Percona Operators for MySQL, PostgreSQL and MongoDB enable cross‑cloud moves by automating real primitives: MySQL uses asynchronous replication between Percona XtraDB clusters (works with MySQL 8 / pre‑8.22 failover), MongoDB adds remote nodes to expand replica set membership as unmanaged nodes, Postgres uses pgBackRest continuous restore to a standby cluster, and Kubernetes MCS hides networking via MCS service‑imports. Demo migrates a single‑node DigitalOcean MongoDB into Kubernetes, flips primary and hands control to the operator — it succeeds.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:29Databases on Kubernetes - 2 components
- 2:47Why Operators
- 5:13Operator basics
- 6:30Percona Operators
- 7:57Why multi-cloud
- 10:11Multi-cloud for databases
- 10:56Add Kubernetes
- 13:12MySQL multi-cloud overview
- 16:23MySQL example
- 17:08MongoDB multi-cloud overview
- 18:03MongoDB example
- 18:38PostgreSQL - Overview
- 20:39PostgreSQL - example
- 21:54Multi-cluster Services
- 30:58Useful links
related talks
31mOpen Source Databases on Kubernetes: Best Practices
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
27mDIY DBaaS with Percona Kubernetes Operators
34mDatabases on Kubernetes
30mComposing a Multi Database DBaaS from Open Source Kubernetes Operators
31mFrom Atlas to EKS How to Stay Sane and Save 45 During a Large‑Scale MongoDB Migration
41mDemocratizing MySQL: From Cloud Managed to Kubernetes Managed
36mFrom a Database in Container to DBaaS on Kubernetes