Debug like a pro on Kubernetes
summary
Golang apps run as single binaries in tiny containers and are debugged with concrete tooling: Prometheus metrics + Telegraf collectors to InfluxDB, OpenCensus/OpenTracing with Jaeger/Zipkin for distributed traces, and CI/GitOps pipelines to apply tested YAML. Built tools include a feature environment generator that provisions namespaced runtime sandboxes, a backup and restore operator for persistent volumes, and an extended pprof/all diagnostic tar that bundles heap, CPU, goroutine and database query snapshots for offline analysis. Traces reveal surprising hotspots like repeated AWS registerInstance retries and direct the exact function to fix.
AI-written summary · about
chapters (16)
- 0:00Start
- 6:16Deploy Your Ci on Kubernetes
- 7:27Tools
- 12:42Git Ops
- 16:18Backup and Restore Operator for Persistent Volumes
- 18:03Instrumentation and Observability
- 22:55Observability Code
- 24:56Prometheus
- 30:35Distributed Tracing
- 31:46Open Tracing
- 35:53Infrastructure for Tracing
- 38:21Runtime Profiling Library
- 46:35Remote Debugging
- 47:22Summarize
- 48:19Overlap between Open Senses and Open Tracing
- 55:20Rules for How You Decide What To Trace and What Kind of Level of Granularity
related talks
34mDebugging at Scale in Production - Deep into Your Containers with Kubectl Debug
40mDebugging in Golang Apps Inside K8s Environment
24mDebugging at Scale in Production - Deep into your Containers
35mA story about debugging of one Go application
31mDebugging Go: from zero to Kubernetes - Michele Caci
50mTroubleshooting & Debugging Microservices in Kubernetes
51mTroubleshooting & Debugging Production Microservices in Kubernetes
35mThe Art of Debugging Inside K8s Environment