<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Preemption on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/preemption/</link>
    <description>Recent content in Preemption on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/preemption/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Priority &amp; Preemption Scheduling: Best Practices &amp; Tools (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-15-kubernetes-priority-preemption-scheduling-best-practices-guide/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-15-kubernetes-priority-preemption-scheduling-best-practices-guide/</guid>
      <description>&lt;p&gt;In a shared Kubernetes cluster, not all workloads are equally important. Production databases should never be evicted to make room for batch jobs. Critical API gateways deserve guaranteed resources over experimental workloads. Kubernetes PriorityClasses and preemption provide the mechanisms to enforce these priorities — but configuring them correctly requires understanding how the scheduler, eviction logic, and resource quotas interact.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
