<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Probes on Daniel Corneschi</title><link>https://blog.corneschi.ro/tags/probes/</link><description>Recent content in Probes on Daniel Corneschi</description><generator>Hugo</generator><language>en</language><copyright>Daniel Corneschi</copyright><lastBuildDate>Wed, 14 Oct 2026 17:52:33 +0300</lastBuildDate><atom:link href="https://blog.corneschi.ro/tags/probes/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Health Checks: Liveness, Readiness, and Startup Probes</title><link>https://blog.corneschi.ro/posts/kubernetes-health-checks-probes/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0300</pubDate><guid>https://blog.corneschi.ro/posts/kubernetes-health-checks-probes/</guid><description>&lt;p&gt;Kubernetes only knows three container states on its own: waiting, running, and terminated. &amp;ldquo;Running&amp;rdquo; just means the process (PID 1) exists — not that the application inside is actually serving requests. Probes close that gap. Without them, a pod is marked Ready the instant its container starts and stays Ready even if the app inside has hung. This article explains what happens without health checks, how each probe works, and how to configure them.&lt;/p&gt;</description></item></channel></rss>