Updating Databases the GitOps Way
summary
Argo CD deployments order database migrations before app rollout by using the open source Atlas operator, which introduces two CRDs: AtlasMigration for versioned migrations and AtlasSchema for declarative schema desired-state. Operator supports MySQL, PostgreSQL, SQLite and MSSQL, auto-plans diffs, runs and exposes status, and offers safety policies and observability (so hooks, init containers or jobs aren’t needed). Demo shows auto-generated SQL diffs, ERD export, and Argo CD sync-wave ordering preventing app startup before migrations finish.
AI-written summary · about
chapters (11)
- 0:00GitOps for databases
- 1:03Manual scripts to GitOps
- 2:29Anti-patterns in migrations
- 4:34Automate migrations
- 5:38Kubernetes solutions flaws
- 8:05Atlas Kubernetes operator
- 13:21Atlas operator workflow demo
- 19:05Advantages of operator
- 20:28Unified GitOps with Argo CD
- 21:32Rollbacks in migrations
- 24:03Q&A on Flyway
related talks
14mBuilding a self service DBaaS
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
27mDecoupling Canary Deployments From DBs With Argo Rollouts
26mManaging GitOps Deployments in Multi-cluster Production Environments
33mAvoid Toll Roads: Deploying Declarative Database Schema Changes
31mBeyond Alembic and Django Migrations
45mEnabling Continuous Delivery with Database Practices