<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Lorbic</title><link>http://localhost:1313/tags/devops/</link><description>Recent content in Devops on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating Cloudflare to Terraform</title><link>http://localhost:1313/cloudflare-management-with-terraform/</link><pubDate>Tue, 28 Apr 2026 14:00:00 +0530</pubDate><guid>http://localhost:1313/cloudflare-management-with-terraform/</guid><description>&lt;p>A while back, I was tinkering in the Cloudflare dashboard and accidentally fat-fingered a DNS configuration. I didn&amp;rsquo;t realize the impact immediately, but I ended up taking down &lt;code>lorbic.com&lt;/code> for an hour.&lt;/p>
&lt;p>When I scrambled to fix it, I hit a wall: there was no &amp;ldquo;undo&amp;rdquo; button. There was no Git history to tell me what the record &lt;em>used&lt;/em> to point to, and no review to catch the mistake before I blew it.&lt;/p></description></item><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><item><title>Fast Docker CI: Stop Rebuilding Container Images on Every Commit</title><link>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</link><pubDate>Sun, 15 Feb 2026 02:30:00 +0530</pubDate><guid>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</guid><description>&lt;p>I used to rebuild my Docker image every time I fixed a typo. A one-line change meant waiting 2-3 minutes for Docker to rebuild layers, reinstall dependencies, and restart the container. I thought this was just the cost of containerized development.&lt;/p>
&lt;p>Then I discovered runtime containers. Same isolated environment, same reproducibility, but code changes reflect instantly. No rebuilds. No waiting. The runtime lives in the container, the code lives on the host.&lt;/p></description></item><item><title>How to Install Docker Desktop on Another Drive in Windows</title><link>http://localhost:1313/docker-custom-installation-location-windows/</link><pubDate>Sat, 27 Jan 2024 13:11:47 +0000</pubDate><guid>http://localhost:1313/docker-custom-installation-location-windows/</guid><description>&lt;p>Docker Desktop on Windows installs to your C: drive by default. When you pull large images (often 1.5GB each), add build layers, and stack containers, the ext4.vhdx file that holds all your container data bloats fast. This guide shows you how to route Docker to a secondary drive entirely, using CLI flags instead of the GUI.&lt;/p>
&lt;h2 id="quick-start">Quick Start&lt;a class="anchorjs-link" href="#quick-start" aria-label="Link to section: Quick Start">&lt;/a>&lt;/h2>&lt;p>Uninstall any existing Docker first. Then open PowerShell as admin and navigate to your Downloads folder where the installer is. Run:&lt;/p></description></item></channel></rss>