<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>readiness on Dileep Kumar</title>
    <link>https://dileepkumar.dev/tags/readiness/</link>
    <description>Recent content in readiness on Dileep Kumar</description>
    <image>
      <title>Dileep Kumar</title>
      <url>https://dileepkumar.dev/papermod-cover.png</url>
      <link>https://dileepkumar.dev/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Jan 2025 00:35:00 +0530</lastBuildDate><atom:link href="https://dileepkumar.dev/tags/readiness/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Health Probes: Liveness, Readiness, and Startup Probes Explained</title>
      <link>https://dileepkumar.dev/post/kubernetes-health-probes/</link>
      <pubDate>Mon, 13 Jan 2025 00:35:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-health-probes/</guid>
      <description>Introduction Kubernetes needs to know when your applications are healthy and ready to serve traffic. Health Probes enable Kubernetes to automatically detect and recover from application failures, ensuring high availability.
Understanding Health Probes The Problem Without Probes:
Crashed applications continue receiving traffic Deadlocked processes never recover Slow-starting apps receive traffic too early Failed containers remain in &amp;ldquo;Running&amp;rdquo; state The Solution: Health probes provide automated health monitoring and recovery:
Automatic restart of failed containers Traffic routing only to healthy pods Graceful startup for slow applications Self-healing without manual intervention Types of Probes - Complete Comparison Probe Type Purpose Action on Failure When to Use Liveness Is container alive?</description>
    </item>
    
  </channel>
</rss>
