<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Configuration-Management on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/configuration-management/</link>
		<description>Recent content in Configuration-Management on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 15 Jul 2026 19:31:37 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/configuration-management/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Common Kubernetes Probe Misconfigurations and Fixes</title>
				<link>https://www.compilemymind.com/posts/kubernetes-probe-misconfigurations-fixes/</link>
				<pubDate>Wed, 15 Jul 2026 19:31:37 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/kubernetes-probe-misconfigurations-fixes/</guid>
				<description>&lt;h2 id=&#34;direct-answer&#34;&gt;Direct answer&lt;/h2&gt;&#xA;&lt;p&gt;Kubernetes probes fail when the check does not match the application&amp;rsquo;s startup time, listening address, endpoint, or expected response. A liveness probe decides whether a container should be restarted, a readiness probe decides whether traffic should be sent, and a startup probe gives a slow-starting container time to initialize before the other checks matter. Diagnose the probe type first, then verify the command, HTTP path, port, and timing values against the running Pod.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
