<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Networking on n8r | Clément</title>
    <link>https://clement.n8r.ch/en/tags/networking/</link>
    <description>Recent content in Networking on n8r | Clément</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 29 Mar 2021 05:42:38 +0100</lastBuildDate>
    <atom:link href="https://clement.n8r.ch/en/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes CNI — deconstructed</title>
      <link>https://clement.n8r.ch/en/articles/kubernetes-cni-deconstructed/</link>
      <pubDate>Mon, 29 Mar 2021 05:42:38 +0100</pubDate>
      <guid>https://clement.n8r.ch/en/articles/kubernetes-cni-deconstructed/</guid>
      <description>&lt;p&gt;A few months ago, I had to understand in detail how Container Network Interface (CNI) is implemented to, well, simply get a chaos testing solution working on a bare-metal installation of Kubernetes.&lt;/p&gt;
&lt;p&gt;At that time, I found a few resources that helped me understand how this was implemented, mainly &lt;a href=&#34;https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/&#34;&gt;Kubernetes&amp;rsquo; official documentation on the topic&lt;/a&gt;, and the &lt;a href=&#34;https://github.com/containernetworking/cni/blob/master/SPEC.md&#34;&gt;official CNI specification&lt;/a&gt;. And yes, this specification simply consists of a Markdown document, which I needed to invest a consequent amount of energy to digest and process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
