Health Checks, Probes and Self-Healing — Kubernetes Orchestration

Self-healing is one of Kubernetes' most valuable operational properties — the system detects and recovers from failures automatically without human intervention. But self-healing only works correctly when Kubernetes has accurate information about the health of each container. The three probe types (liveness, readiness, startup) are the mechanism through which containers communicate their health state to Kubernetes. Poorly configured probes are one of the most common sources of production reliability problems: liveness probes that are too aggressive kill healthy containers during temporary load spikes; readiness probes that don't truly reflect readiness send traffic to containers that aren't ready; missing startup probes cause slow-starting applications to be killed before they finish initialising. This lesson deepens the probe understanding from Lesson 5, focusing on production probe configuration patterns, probe implementation strategies, and the relationship between probes and Pod Disruption Budgets.

Analogy🏏Cricket

🏏 Think of it like cricket: A well-run cricket board has distinct departments with clear responsibilities: the selection committee chooses players, the grounds department prepares venues, the scheduling department assigns matches to grounds, the operations department manages logistics, and the referees enforce the rules. No department does another's job, and all communication flows through the central secretariat. Just as the ICC's effectiveness comes from each department having a clear mandate and working through a central coordination system, Kubernetes' reliability comes from each component (API server, scheduler, controller manager, etcd, kubelet, kube-proxy) having a single responsibility and communicating only through the API server as the central hub. The insight is that this architecture makes the system resilient: a failure in the scheduling department doesn't stop ongoing matches, just as a failing scheduler doesn't kill running Pods.