Troubleshooting & Debugging Microservices in Kubernetes
summary
Demo guestbook app runs on a five‑node GKE cluster and surfaces 404/500 errors. Troubleshooting workflow: compare container image SHAs (don’t rely on latest), inspect aggregated logs via Fluentd → Stackdriver and query them with BigQuery to find the offending pod, stream logs with Stern, take the bad pod out of service by flipping a label, kubectl exec / kubectl port‑forward for live checks, visualize calls with Weave Scope and Zipkin/Jaeger tracing, and attach a debugger or use snapshot debugging to capture state.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:58Demo application
- 4:50Deploying in Communities
- 6:16Load Balancer
- 8:27Namespace
- 9:52Demo
- 11:17Staging
- 11:45Staging and prod
- 13:41Inspecting containers
- 14:02Configuring the backend
- 15:11Getting into production
- 16:27Metadata
- 19:20Logs
- 23:12Centralized Logging
- 24:17Centralized Logging Exceptions
- 28:29Restarting Microservices
- 29:22Cronjobs
- 32:19Investigating the issue
- 33:38Port forwarding
- 35:15Scaling down
- 36:47Service topology
- 39:11Digital tracing
- 41:36What would you do
- 43:28Debugger agent
related talks
50mTroubleshooting & Debugging Microservices in Kubernetes
51mTroubleshooting & Debugging Production Microservices in Kubernetes
53mDebugging and Troubleshooting Java-based Microservices in Kubernetes
30mStreamlined Troubleshooting in Kubernetes
34mChaos Debugging: Finding and Fixing Microservice Weak Points
01h 32mTutorial: Debug Your Kubernetes Apps
49mDeveloping microservices applications on the Kubernetes platform
46mFrom Docker To Kubernetes: A Developer's Guide To Containers