Debugging in Golang Apps Inside K8s Environment
summary
Shows a practical workflow for debugging Go binaries inside Kubernetes by baking Delve into images, toggling an entrypoint with an env var, and running dlv headless+port-forward to attach from a laptop. Covers multi‑stage images (keep DWARF info), substituting local source paths for correct mapping, and using kubectl debug shared PID or a K9s plugin to spawn a sidecar with networking and sources. Demos connect, set conditional breakpoints, restart the process, and generally work—watch for matching commit SHAs and reduced traffic during a session.
AI-written summary · about
chapters (9)
- 0:00Debugging Go apps in Kubernetes
- 1:26Debugging hardest part
- 5:26Delve for container debugging
- 10:59Multi-stage Docker images
- 18:14Remote debugging binaries
- 23:59Debugging in Kubernetes
- 30:31Kubernetes debugging tips
- 33:47Resources
- 34:29Q&A
related talks
31mDebugging Go: from zero to Kubernetes - Michele Caci
35mThe Art of Debugging Inside K8s Environment
34mDebugging at Scale in Production - Deep into Your Containers with Kubectl Debug
36mEphemeral Containers in Action - Running a Go Debugger in Kubernetes - Marvin Beckers
01h 00mDebug like a pro on Kubernetes
24mDebugging at Scale in Production - Deep into your Containers
34mDebugging python applications inside k8s environment
39mDebugging python applications inside k8s environment
