<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spiderpool on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/spiderpool/</link>
    <description>Recent content in Spiderpool on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/spiderpool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes CNI: Antrea vs Kube-OVN vs Spiderpool (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-10-self-hosted-kubernetes-cni-antrea-kube-ovn-spiderpool-guide/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-10-self-hosted-kubernetes-cni-antrea-kube-ovn-spiderpool-guide/</guid>
      <description>&lt;p&gt;The Container Network Interface (CNI) is the networking backbone of every Kubernetes cluster. While default plugins like Flannel provide basic pod-to-pod connectivity, production workloads demand advanced features: network policies, load balancing, BGP routing, multi-homing, and hardware acceleration. The choice of CNI directly impacts cluster performance, security posture, and operational complexity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
