From Villains to Heroes: How an Improved DX Has Made Our Devs...
summary
InfluxData replaces local kind/Docker desktop workflows with per-developer GKE namespaces and a toolchain built on garden.io + telepresence.io, invoked via make deploy remote and `make remote_dev`. Backend code syncs and rebuilds remotely (binary restarts in pods), front end uses a telepresence reverse proxy to a local webpack dev server, cutting local resource use and enabling hundreds of namespaces. Early issues include telepresence robustness and garden missing jsonnet/CRD support (solved with generated YAML and pod selectors); stability and communication remain work in progress.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53About Influx Data
- 9:53About Remotel
- 14:48The 4 Development Experience Pillars
- 15:32Clarity
- 17:10Stability
- 18:23Challenges
- 20:31Local Development Environment
- 21:07Feedback
- 22:13Happyish
related talks
27mNavigating the Shift to Remote Developer Environments - A Year of Insights and Challenges
42mUse Your Favorite Developer Tools in Kubernetes With Telepresence
26mClosing the Developer Experience Gap of K8s Development
24mRemote development can improve your developers remote work experience
34mLocal Microservice Development: Remote Kubernetes Assist
31mEnvironments as a Service: improve DX
22mDX for Internal Teams
44mCloud Native Applications with Remote Development Environments