<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>CNI - Tag - vo.rs</title><link>https://vo.rs/tags/cni/</link><description>CNI - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 08 Oct 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/cni/" rel="self" type="application/rss+xml"/><item><title>Calico vs Cilium: Kubernetes CNI for a Home Cluster</title><link>https://vo.rs/story/calico-vs-cilium-kubernetes-cni-for-a-home-cluster/</link><description>&lt;p&gt;Set up a fresh Kubernetes cluster and one of the first decisions you&amp;rsquo;re handed is also one of the least explained: which CNI? Your nodes sit there in &lt;code&gt;NotReady&lt;/code&gt;, the docs wave vaguely at a list, and you pick whatever the tutorial used. Months later you&amp;rsquo;re trying to write a NetworkPolicy or debug a packet that vanishes, and you finally wish you&amp;rsquo;d understood the choice.&lt;/p&gt;
&lt;p&gt;The Container Network Interface is the plugin that gives every pod an IP and makes pods on different nodes able to talk to each other. Without one, your cluster is a collection of isolated boxes. For self-hosters, two names dominate the conversation: &lt;strong&gt;Calico&lt;/strong&gt; and &lt;strong&gt;Cilium&lt;/strong&gt;. They reach the same destination by very different roads.&lt;/p&gt;</description><pubDate>Tue, 08 Oct 2024 09:00:00 +0000</pubDate></item></channel></rss>