<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Job-Queue on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/job-queue/</link>
    <description>Recent content in Job-Queue 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/job-queue/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Batch Job Management: Queue Systems, Operators &amp; Orchestrators</title>
      <link>https://www.pistack.xyz/posts/2026-05-20-self-hosted-kubernetes-batch-job-management-queue-systems-operators-orchestrators/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-20-self-hosted-kubernetes-batch-job-management-queue-systems-operators-orchestrators/</guid>
      <description>&lt;p&gt;Kubernetes Jobs are designed for batch workloads — finite tasks that run to completion and terminate. But when you&amp;rsquo;re running hundreds of batch jobs per day for ML training, data processing, or CI/CD pipelines, the native Job controller becomes a bottleneck. You need queueing, priority management, gang scheduling (all-or-nothing scheduling for multi-pod jobs), and fair resource sharing across teams.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
