Successful Kubernetes Development Workflows
summary
Compares concrete workflows: Datadog runs a remote cluster for ~300 services and uses Tilt plus Helm to pull CI images, add developer buttons for DB flushes and achieves team-wide automation; Cluster API uses kind locally for frequent tear-downs and contributed a cert-manager extension as a Tilt extension; a 4-person scooter team runs Docker for Mac and copies uniform Helm charts. Emphasizes reducing a 30 minute build loop toward two second feedback via live updates and Tilt snapshot links for shareable debugging.
AI-written summary · about
chapters (11)
- 0:00Intro
- 4:24WHOAMI
- 4:57The problem set
- 5:21The protagonists
- 6:33Development clusters
- 13:55Managing configuration files
- 17:07Feedback loop automation
- 25:28Problem solving (single player)
- 28:47Problem solving (multi player)
- 32:09Custom workflows
- 35:35Outro
related talks
13mInterview of Jerome Petazzoni
42mDeveloper-first Workflows on Kubernetes
47mKubernetes Day 3: The State of Kubernetes Development Tooling
37mDesigning Cloud Ready Applications
45mKubernetes Operability Tooling
57mReal-World Kubernetes For DevOps
01h 00mJava on Kubernetes What I Wish I Knew First
55mFrom my Machine to the Cloud with Cloud-Native Tools