<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Lorbic</title><link>http://localhost:1313/categories/infrastructure/</link><description>Recent content in Infrastructure on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 22:00:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/categories/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes on WSL2 and the macOS tunnel</title><link>http://localhost:1313/kubernetes-on-wsl2-macos-access/</link><pubDate>Wed, 01 Apr 2026 22:00:00 +0530</pubDate><guid>http://localhost:1313/kubernetes-on-wsl2-macos-access/</guid><description>&lt;p>&lt;strong>TL;DR:&lt;/strong> I run &lt;strong>k3s&lt;/strong> on a Windows gaming PC via &lt;strong>WSL2&lt;/strong> to master Kubernetes networking without cloud costs. This guide details a secure access model using &lt;strong>SSH&lt;/strong> and &lt;strong>kubectl port-forward&lt;/strong> to bypass NAT boundaries and maintain technical sovereignty.&lt;/p>
&lt;hr>
&lt;p>This guide omits Kubernetes feature tutorials. Instead, it details how to architect an environment where Kubernetes can exist without auxiliary hardware, idle cloud bills, or hidden networking realities.&lt;/p>
&lt;p>I wanted to learn Kubernetes properly, which meant understanding how &lt;strong>scheduling&lt;/strong>, &lt;strong>access paths&lt;/strong>, and &lt;strong>network boundaries&lt;/strong> behave under real constraints. The problem was simple: I lacked a reasonable execution environment.&lt;/p></description></item></channel></rss>