Kubectl Said What?
summary
Shows exact kubectl commands and fields to inspect real failures: use kubectl get with -o yaml/json and jsonpath, check kubectl describe for events, and query status.conditions to extract the message. Walks through concrete scenarios: ReplicaSet events exposing quota and missing serviceAccount errors, scheduler failures like Insufficient CPU/memory or volume binding, container states (waiting, crashloop, restartCount) and probe vs kubelet-down cases where pods report Running but are Unready. Practical, command-level debugging examples.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:06Resource Creation Flow
- 2:28Deciphering kubectl's Messages
- 4:16Controllers: Example
- 4:31Controllers: Conditions
- 14:34Pods: Phases
- 22:25Running Pods, Containers: States
- 30:34Running: Examples
related talks
35mCrashLoopBackoff, Pending, FailedMount and Friends: Debugging Common Kubernetes Cluster
28m11 tricks to improve productivity and reduce your frustration with Kubernetes
19mUnleashing the power of kubectl
30mManaging Kubernetes Without Losing Your Cool
25mIn Search Of A `kubectl blame` Command
10mKeynote: Unleashing the Power of Kubectl
24mDebugging at Scale in Production - Deep into your Containers
45mTroubleshooting containerized applications