<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sai Pisey - Blog</title>
    <link>https://saipisey.com/blog</link>
    <description>Field notes from production Kubernetes and from fixes merged upstream.</description>
    <language>en</language>
    <atom:link href="https://saipisey.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your cluster says 3/3. It will still go dark with one zone.</title>
      <link>https://saipisey.com/blog/kubectl-survive-zone</link>
      <guid isPermaLink="true">https://saipisey.com/blog/kubectl-survive-zone</guid>
      <pubDate>Sat, 03 Oct 2026 18:30:00 GMT</pubDate>
      <description>Manifests describe intent; the cluster holds placement. How kubectl survive-zone proves which workloads stop serving when a zone dies, and why a perfectly spread deployment can still go down.</description>
      <category>Kubernetes</category>
      <category>Scheduling</category>
      <category>Reliability</category>
    </item>
  </channel>
</rss>
