https://nibblesnbits.org/posts/Recent content in Posts on Nibbles & BitsHugo -- 0.155.0en-usThu, 29 Jan 2026 10:51:38 -0500https://nibblesnbits.org/posts/mikrotikproxmoxvlan/Thu, 29 Jan 2026 10:51:38 -0500https://nibblesnbits.org/posts/mikrotikproxmoxvlan/<p>Setting up a home lab or a production environment for Kubernetes often requires network segmentation. Using VLANs (Virtual LANs) allows you to isolate your K8s traffic from your general house or office traffic.</p> <p>In this guide, we will configure a <strong>MikroTik Router</strong> to trunk two VLANs (100 and 300) over a single cable to a <strong>Proxmox</strong> host, specifically optimized for automated provisioning and security.</p> <h2 id="why-isolate-kubernetes-traffic">Why Isolate Kubernetes Traffic?</h2> <p>Isolating Kubernetes into its own VLAN (like VLAN 300) isn&rsquo;t just about tidiness; it’s a security and operational necessity:</p>https://nibblesnbits.org/posts/cicdwebsite/Tue, 27 Jan 2026 20:22:20 -0500https://nibblesnbits.org/posts/cicdwebsite/<h1 id="multi-arch-cicd-building-a-hugo-nginx-container">Multi-Arch CI/CD: Building a Hugo Nginx Container</h1> <p>This write-up covers the transition from local Hugo builds to an automated, multi-architecture (AMD64/ARM64) Docker pipeline using GitHub Actions and Docker Hub.</p> <h2 id="the-problem">The Problem</h2> <p>I wanted to simplify my website development. Rather than focusing on infrastructure, I wanted to focus on content. I chose Hugo because it allows me to create simple Markdown files while generating an elegant, high-performance site.</p> <p>However, traditional deployment often involves manual rsyncing or running Hugo directly on a production server. This creates &ldquo;it works on my machine&rdquo; issues and makes architecture-specific deployments (like moving to an ARM64 server) a logistical headache.</p>