Forklifting Django: Migrating A Complex Django App To Kubernetes
summary
A Django monolith with Celery, Channels, Postgres, Redis and RabbitMQ gets lifted into Kubernetes using multi-stage Docker builds and initial manual YAML then Helm then a homegrown solution: a custom Kubernetes operator implemented in Go that exposes a CRD, runs a reconcile loop and enforces a simple state machine (initializing → migrating → deploying → ready → error). Development uses a Postgres operator, production uses RDS, migrations and ordering are automated, GitOps (repo → Argo CD → operator) records deployments and reduces drift.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:48Terminology
- 4:53Container Image
- 8:50Helm
- 13:00Watch
- 15:15Why does this matter
- 17:56Coding
- 20:17Celery Beets
- 23:37Workflow
- 24:49Drift
- 28:28Conclusion
related talks
29mForklifting Django: Migrating A Complex Django App To Kubernetes
38mEnd-to-End Django on Kubernetes
49mFundamentals of Kubernetes for Django developers
44mMigrating a Monolith to Kubernetes
32mKubernetes as LEGO: Building Platforms one block at a time
44mA Django Project Template with CI/CD Pipelines and k8s Orchestration
26mDeploy Python Apps on Kubernetes and Prepare for Scale
31mSimplifying Python Web App Operations: Automating K8s Ops with Open Source