Keep Calm and Troubleshoot Your Deployments
summary
Demo breaks two small apps and then fixes them live: first app fails because a required environment variable is missing — add the env var and the pod serves traffic; second app returns 502 because container listens on port 9898 while Service/Ingress target uses 8080 — changing the Service/targetPort to 9898 fixes it. Workflow uses kubectl get/describe, kubectl logs and kubectl port-forward to confirm pod health and connectivity and watches for endpoints empty to find service wiring issues.
AI-written summary · about
chapters (8)
- 0:00Troubleshooting deployments
- 1:03Kubernetes deployment basics
- 11:24Rolling updates in Kubernetes
- 16:01Deployment debugging pitfalls
- 17:25Broken deployment debugging
- 22:49Service and port fixes
- 28:33Endpoints and routing
- 31:00Debugging best practices
related talks
50mTroubleshooting & Debugging Microservices in Kubernetes
45mTroubleshooting containerized applications
50mTroubleshooting & Debugging Microservices in Kubernetes
30mAfterlife tales: Troubleshooting containerized applications
51mTroubleshooting & Debugging Production Microservices in Kubernetes
35mThe Art of Debugging Inside K8s Environment
46mModern DevOps with Kubernetes
40mHarnessing Kubernetes to Manage Containerized Microservices at Scale
