<?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 MLog</title><link>http://blog.ghanmi.me/tags/cni/</link><description>Recent content in Cni on MLog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 24 Mar 2026 01:38:01 +0100</lastBuildDate><atom:link href="http://blog.ghanmi.me/tags/cni/index.xml" rel="self" type="application/rss+xml"/><item><title>a simple k8s Network Plugin with eBPF</title><link>http://blog.ghanmi.me/posts/building-k8s-cni-plugin-with-ebpf/</link><pubDate>Tue, 03 Sep 2024 00:00:00 +0000</pubDate><guid>http://blog.ghanmi.me/posts/building-k8s-cni-plugin-with-ebpf/</guid><description>Prerequisites A working Kubernetes cluster for testing (a single-node kind or kubeadm cluster works perfectly) clang/llvm for compiling eBPF programs, bpftool What We&amp;rsquo;re Building Our plugin will handle a single, well-defined scope: pod-to-pod connectivity on a single node. That means every pod gets an IP address, and any pod can reach any other pod on the same machine. We won&amp;rsquo;t handle multi-node routing, services, or network policy. each of those is a project unto itself.</description></item></channel></rss>