<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubelet on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/kubelet/</link><description>Recent content in Kubelet on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 17:01:10 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/kubelet/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubelet inode monitoring: reactive, not proactive, on worker nodes</title><link>https://curadevops.metacog.co.kr/insights/2026-10-06-kubelet-watches-inodes-just-not-until-it-s-an-emergency/</link><pubDate>Tue, 06 Oct 2026 17:01:10 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-06-kubelet-watches-inodes-just-not-until-it-s-an-emergency/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Explains a gap in how Kubelet surfaces inode exhaustion — it alerts only when already in critical territory, not proactively. Worth factoring into NodeFilesystemFilesFillingUp alert tuning and inode-capacity headroom planning on worker nodes.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>