<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cni on Pi Stack</title><link>https://www.pistack.xyz/tags/cni/</link><description>Recent content in Cni on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/cni/index.xml" rel="self" type="application/rss+xml"/><item><title>Flannel vs Calico vs Cilium: Best Kubernetes CNI Plugins 2026</title><link>https://www.pistack.xyz/posts/2026-04-21-flannel-vs-calico-vs-cilium-self-hosted-kubernetes-cni-guide-2026/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-21-flannel-vs-calico-vs-cilium-self-hosted-kubernetes-cni-guide-2026/</guid><description>&lt;p>Every Kubernetes cluster needs a Container Network Interface (CNI) plugin to handle pod-to-pod communication, service discovery, and network policy enforcement. Choosing the right CNI is one of the most impactful infrastructure decisions you&amp;rsquo;ll make — it affects network performance, security posture, operational complexity, and the features available to your workloads.&lt;/p></description></item></channel></rss>