<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Stateful-Workloads on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/stateful-workloads/</link>
    <description>Recent content in Stateful-Workloads on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/stateful-workloads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes StatefulSet Management: Operators, Backup &amp; Scaling Tools</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-kubernetes-statefulset-management-operators-backup-scaling-guide/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-kubernetes-statefulset-management-operators-backup-scaling-guide/</guid>
      <description>&lt;p&gt;Kubernetes StatefulSets are the go-to workload type for running stateful applications — databases, message queues, and any service that requires stable network identity, persistent storage, and ordered deployment. But managing StatefulSets at scale introduces challenges that the native Kubernetes API doesn&amp;rsquo;t fully address: automated backup and restore, horizontal scaling, version upgrades, and failure recovery.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
