<?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>kubernetes on ashikov.ru</title><link>https://ashikov.ru/en/tags/kubernetes/</link><description>Recent content in kubernetes on ashikov.ru</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ashikov.ru/en/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>How an inotify watchers limit caused kubelet instability</title><link>https://ashikov.ru/en/notes/inotify-watchers-kubelet-instability/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/inotify-watchers-kubelet-instability/</guid><description>Troubleshooting an unstable Kubernetes node caused by an exhausted inotify watchers limit.</description></item><item><title>Who consumes inotify watchers in Kubernetes</title><link>https://ashikov.ru/en/notes/who-consumes-inotify-watchers/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/who-consumes-inotify-watchers/</guid><description>An overview of the processes that consume inotify watchers and why this Linux limit should be part of infrastructure capacity planning.</description></item></channel></rss>