<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wireguard on johanneskueber.com</title><link>https://johanneskueber.com/tags/wireguard/</link><description>Recent content in Wireguard on johanneskueber.com</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://johanneskueber.com/tags/wireguard/index.xml" rel="self" type="application/rss+xml"/><item><title>Running a rootless NetBird Routing Peer Inside Kubernetes</title><link>https://johanneskueber.com/posts/2026-05-25-netbird-routing-peer/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><guid>https://johanneskueber.com/posts/2026-05-25-netbird-routing-peer/</guid><description>&lt;p&gt;This article documents how to run a NetBird client &lt;em&gt;inside&lt;/em&gt; a Kubernetes cluster as a &lt;strong&gt;routing peer&lt;/strong&gt; — rootless, with an in-memory state volume, a shell-based readiness probe, and dropped capabilities — so that remote mesh members can reach cluster-internal services over the encrypted overlay, without exposing kernel WireGuard and without making the cluster a peer of every workload.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-why-a-netbird-peer-in-the-cluster"&gt;1. Why a NetBird peer in the cluster&lt;/h2&gt;
&lt;p&gt;NetBird is a WireGuard-based identity mesh. Each peer holds keys, exchanges them via the management plane, and routes encrypted traffic to other peers. The default deployment runs the client on a host (Linux VM, MacBook, etc.) and uses the host&amp;rsquo;s kernel WireGuard.&lt;/p&gt;</description></item></channel></rss>