Closing the Developer Experience Gap of K8s Development
summary
Kubernetes development suffers a slower inner loop—iterations drop from about 70 to 14 once code must be containerized, pushed and deployed. Telepresence is a CNCF two-way proxy that routes cluster traffic to a local service so developers run only the service under change while depending services stay remote. It supports global and personal intercepts (subset-by-header) and demos show live UI flips (green→blue→orange) instantly after local edits. A cited team stops running all microservices locally and replaces build/push/deploy with code→intercept→test.
AI-written summary · about
chapters (22)
- 0:00intro
- 0:27preamble
- 0:59kubernetes has solved many business challenges
- 1:43what's developer experience?
- 2:15inner & outer loops
- 2:57cloud native technologies have altered the devex
- 3:57traditional inner dev loop
- 4:59container inner dev loop
- 6:28a slow inner dev loop impacts everyone
- 7:29is there a way out?
- 7:45local development
- 9:28remote development
- 11:19telepresence
- 11:48remocal development
- 12:57what is telepresence?
- 13:24global / personal
- 14:15how does telepresence work?
- 15:43demo time
- 22:57without telepresence / with telepresence
- 24:23wrapping up
- 25:19try telepresence today!
- 25:39thank you!
related talks
28mFrom Network Engineer to K8s Developer: Lessons Learned via Telepresence
42mUse Your Favorite Developer Tools in Kubernetes With Telepresence
36mSeamless Development Environments on Kubernetes using Telepresence - Ara Pulido
30mIntro: Telepresence
31mIntro: Telepresence
44mCloud Native Applications with Remote Development Environments
46mIn Search of the Perfect Cloud Native Developer Experience
54mClosing the Developer Experience Gap in the Kubernetes Ecosystem