<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workload-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/workload-management/</link>
    <description>Recent content in Workload-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/workload-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Advanced Workload Controllers: OpenKruise vs Argo Rollouts vs Flagger</title>
      <link>https://www.pistack.xyz/posts/2026-05-17-self-hosted-kubernetes-workload-controllers-openkruise-argo-rollouts-flagger-guide/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-17-self-hosted-kubernetes-workload-controllers-openkruise-argo-rollouts-flagger-guide/</guid>
      <description>&lt;p&gt;When managing large-scale Kubernetes deployments, the native Deployment and StatefulSet controllers often fall short. Features like in-place updates, batch pod deletion, calculated pod destruction ordering, and advanced canary releases require extending Kubernetes with custom workload controllers. This guide compares three leading approaches: &lt;strong&gt;OpenKruise&lt;/strong&gt;, &lt;strong&gt;Argo Rollouts&lt;/strong&gt;, and &lt;strong&gt;Flagger&lt;/strong&gt; — each solving different aspects of advanced workload management on self-hosted Kubernetes clusters.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
