<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Practical K3s: Building a Hybrid Cloud Architecture From Scratch on VinhMDev</title><link>https://vinhmdev.com/series/practical-k3s-building-a-hybrid-cloud-architecture-from-scratch/</link><description>Recent content in Practical K3s: Building a Hybrid Cloud Architecture From Scratch on VinhMDev</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vinhmdev.com/series/practical-k3s-building-a-hybrid-cloud-architecture-from-scratch/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 1: The Transition Guide from Docker to Orchestration</title><link>https://vinhmdev.com/posts/part-1-the-transition-guide-from-docker-to-orchestration/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://vinhmdev.com/posts/part-1-the-transition-guide-from-docker-to-orchestration/</guid><description>&lt;h2 id="the-turning-point-from-the-docker-box-to-a-true-system" class="relative group"&gt;The Turning Point: From the Docker Box to a True System &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#the-turning-point-from-the-docker-box-to-a-true-system" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;Following up on our somewhat ironically amusing network incident in the introduction, today we will dive deep into the &amp;ldquo;main character&amp;rdquo; that is carrying the system behind the scenes: K3s.&lt;/p&gt;
&lt;p&gt;If you are used to typing commands and running a few Docker containers on a VPS, everything seems smooth. However, when the application grows and needs to run across 3 to 4 different servers, you will be shocked to realize that pure Docker is simply not enough. A broken cable, a power outage, or just a node catching fire — who will automatically move your application to a healthy node? That&amp;rsquo;s exactly when we need Orchestration, specifically the Kubernetes ecosystem.&lt;/p&gt;</description></item><item><title>Intro: A Tale of 2 Servers, UDP Ports, and K3s</title><link>https://vinhmdev.com/posts/intro-a-tale-of-2-servers-udp-ports-and-k3s/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://vinhmdev.com/posts/intro-a-tale-of-2-servers-udp-ports-and-k3s/</guid><description>&lt;h2 id="the-unintended-cluster-origin" class="relative group"&gt;The Unintended Cluster Origin &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#the-unintended-cluster-origin" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;It all started with an incident that was somewhat&amp;hellip; ironically amusing.&lt;/p&gt;
&lt;p&gt;I had a web project that needed to be deployed urgently. Instead of renting a VPS online as usual, I texted a senior friend in the industry to ask if he had any spare servers to let me use. Very enthusiastically, he immediately threw me the details of a server to get to work.&lt;/p&gt;</description></item></channel></rss>