<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Proxmox on Nibbles &amp; Bits</title><link>https://nibblesnbits.org/tags/proxmox/</link><description>Recent content in Proxmox on Nibbles &amp; Bits</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Thu, 29 Jan 2026 10:51:38 -0500</lastBuildDate><atom:link href="https://nibblesnbits.org/tags/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-VLAN Trunking: Connecting MikroTik to Proxmox for Kubernetes</title><link>https://nibblesnbits.org/posts/mikrotikproxmoxvlan/</link><pubDate>Thu, 29 Jan 2026 10:51:38 -0500</pubDate><guid>https://nibblesnbits.org/posts/mikrotikproxmoxvlan/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;In this guide, we will configure a &lt;strong&gt;MikroTik Router&lt;/strong&gt; to trunk two VLANs (100 and 300) over a single cable to a &lt;strong&gt;Proxmox&lt;/strong&gt; host, specifically optimized for automated provisioning and security.&lt;/p&gt;
&lt;h2 id="why-isolate-kubernetes-traffic"&gt;Why Isolate Kubernetes Traffic?&lt;/h2&gt;
&lt;p&gt;Isolating Kubernetes into its own VLAN (like VLAN 300) isn&amp;rsquo;t just about tidiness; it’s a security and operational necessity:&lt;/p&gt;</description></item></channel></rss>