<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disruption-Budget on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/disruption-budget/</link>
    <description>Recent content in Disruption-Budget on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/disruption-budget/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Pod Disruption Budget Management: Native PDB vs Chaos Engineering Tools — Ensuring High Availability During Disruptions (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-k8s-pod-disruption-budget-management-native-pdb-vs-chaos-engineering-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-k8s-pod-disruption-budget-management-native-pdb-vs-chaos-engineering-guide/</guid>
      <description>&lt;p&gt;When Kubernetes performs voluntary disruptions — node drains during upgrades, cluster autoscaler scaling down unused nodes, or administrators manually evicting pods — there&amp;rsquo;s a risk of taking down too many replicas of a critical service simultaneously. Without proper safeguards, a rolling update could leave your database with zero available pods or your API gateway completely unreachable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
