<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multus on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/multus/</link>
    <description>Recent content in Multus on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/multus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Multi-Network CNI: Multus vs Whereabouts vs CNI Plugins (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-09-kubernetes-multi-network-cni-multus-whereabouts-guide/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-09-kubernetes-multi-network-cni-multus-whereabouts-guide/</guid>
      <description>&lt;p&gt;Running Kubernetes workloads that need more than one network interface — such as DPDK packet processing, SR-IOV virtual functions, or isolated storage networks — requires a CNI solution beyond the standard single-network setup. While default CNIs like Calico, Cilium, and Flannel handle pod-to-pod communication, they do not support attaching multiple interfaces to a single pod.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
