From the course: Debugging Kubernetes

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Debugging failing liveness probes

Debugging failing liveness probes - Kubernetes Tutorial

From the course: Debugging Kubernetes

Start my 1-month free trial Buy for my team

Debugging failing liveness probes

“

- Let's run kubectl get pods to revisit where we left off. In the last video we solved for test-app-2, which had a sneaky exit one command that was causing this pod to enter it's crash loop back off. So now we just need to fix test-app-1. But before we dig into that, let's learn a little bit more about livenessProbes, a powerful technique that Kubernetes uses to ensure that applications are really up and running. LivenessProbes test whether containers in a pod are really started. This is useful for applications that have conditions that need to be met before they can start doing things. There are multiple different kinds of livenessProbes, including HTTP, TCP, and gRPC-based probes. But for this course we're going to stick to a single command based probe called exec. These are defined in the livenessProbe property within the pods, pod specification or pod spec. These probes are executed automatically by the kubelet from outside of your pod on a schedule. This happens every second by…

Contents