DevOps never sleeps. What we learned from InfluxDB v1 to v2
summary
A company moves InfluxDB from v1 to a cloud-first v2 and reports concrete operational lessons: migrated 20 developers onto a cloud project, replaced huge Kubernetes YAML with Go objects and a generator, runs a custom Go orchestrator provisioning thousands of EC2 nodes via AWS APIs, and uses Prometheus Telegraf Chronograf Kapacitor and Jaeger for metrics tracing and alerts. CI runs on Kubernetes, containerd/runC are the runtime layers, and API-driven automation plus instrumentation are the measurable outcomes that actually made the migration work.
AI-written summary · about
chapters (12)
- 0:00Start
- 8:18We need to make our hands dirty
- 9:13Deploy CI on Kubernetes
- 10:30Run your code in prod
- 14:54The secret of success
- 15:58Why Kubernetes is so powerful, complex and widely adopted?
- 16:09Why AWS is so expensive?
- 16:46What do you do to justify these costs?
- 17:18API are the keys for your success!
- 18:43containerd
- 27:02UX for OPS. Because everyone needs to feel like at home...
- 29:03Instrumentation, observability and monitoring
related talks
34mFrom a Backend Developer to DevOps - THE FORCE AWAKENS
40mDevOps is for startups!Enterprises do platform engineering and here is why - Jürgen Süßner
12mKeynote: What It's Like to Bring DevOps to a Software Factory in Central America
25mThe History of DevOps in 30 minutes
55mDevOps @Scale (Greek Tragedy in 3 Acts)
48mDevops@Scale
41mFrom Traditional to GitOps: A Tale of Modernizing Two Goverment Institutions in One Year
36mDevOps in Outsource… Really!