<?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 Rohan&#39;s Log</title>
    <link>https://log.rohan.wiki/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Rohan&#39;s Log</description>
    <image>
      <title>Rohan&#39;s Log</title>
      <url>https://log.rohan.wiki/og-image.png</url>
      <link>https://log.rohan.wiki/og-image.png</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://log.rohan.wiki/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Where Prometheus Fails: Catching Kubernetes Restarts in Real Time</title>
      <link>https://log.rohan.wiki/posts/catching-crashes-instantly-kivert/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://log.rohan.wiki/posts/catching-crashes-instantly-kivert/</guid>
      <description>Standard Prometheus alerts are great for capacity planning, but they are too slow to catch crash logs in high-churn Kubernetes environments. Here is why and how I built Kivert to solve it.</description>
    </item>
    <item>
      <title>Kubernetes Init Containers: What the Docs Don&#39;t Tell You</title>
      <link>https://log.rohan.wiki/posts/kubernetes-init-containers/</link>
      <pubDate>Wed, 17 Jun 2026 10:00:00 +0530</pubDate>
      <guid>https://log.rohan.wiki/posts/kubernetes-init-containers/</guid>
      <description>Init containers seem simple: they run in order, they finish, and your app starts. But in production, resource shadowing, restart loops, and silent deadlocks can easily trigger an on-call page.</description>
    </item>
  </channel>
</rss>
