Introduction I’ve built many projects on my own, but I never shared them publicly. For a long time, I wanted to have my own server with a personal domain name. Unfortunately, for personal reasons, I couldn’t maintain a persistent server. Recently, I discovered a solution that lets me host a blog within minutes using Hugo and GitHub — so here I am. My Linkedin You can see my Linkedin if you want. ...
Here is an improved, smoother, more coherent version of the blog section. Your story stays fully in first-person, as you requested for the blog itself, while you (the reader) are addressed in the third person, as required by your interaction rules. ⸻ My First Homelab (for the second attempt) This homelab is the first real infrastructure I’m building—although technically, it’s already my second attempt. Why a Second Attempt? The first time I tried to set everything up, I used Proxmox running on a VM provider and Talos Linux for my Kubernetes nodes. I experimented with countless configurations, trying to understand how Talos works behind the scenes. Each time a node failed or something didn’t behave the way I expected, I had to rebuild everything manually, one node at a time. It was painful, slow, and sometimes discouraging… but I learned a lot from it. ...
Building a Home Lab to Learn Kubernetes I wanted to learn Kubernetes—really learn it, not just follow a few tutorials. While researching, I noticed many people build their own home labs to run cloud services or custom applications. That inspired me to set up a complete home lab myself: first to run basic services like Nextcloud or OpenProject, and then to experiment with a full DevSecOps pipeline. First Step To understand Kubernetes properly, I needed something close to real-world infrastructure. Buying three or more physical servers wasn’t possible, so I decided to create everything on a single machine using multiple virtual machines (VMs). This way I can spin up as many servers as I need and quickly learn how to build a cluster. ...
First issue Multiples environnements First, I need to connect to my server in SSH and in http to manage Proxmox. With this diagram you can see a simple usage of VM machine. But, I have personal conditions. I need to have a virtual network to have a stable IP of my node in my cluster. But, as you can see, in default with proxmox, you have one bridge created connect to the physical Ethernet port in the server. And, I change environnement to work in my office, and my home because I don’t have an internet box in there, so for connect my server to my PC, I need to connect the Ethernet ports of the server and my PC in direct. ...
First issue Multiples environnements First, I need to connect to my server in SSH and in http to manage Proxmox. With this diagram you can see a simple usage of VM machine. But, I have personal conditions. I need to have a virtual network to have a stable IP of my node in my cluster. But, as you can see, in default with proxmox, you have one bridge created connect to the physical Ethernet port in the server. And, I change environnement to work in my office, and my home because I don’t have an internet box in there, so for connect my server to my PC, I need to connect the Ethernet ports of the server and my PC in direct. ...
Create a Home Lab to Learn Kubernetes Why Learn Kubernetes? swit As a software engineer focused on low-level implementations, I realized I didn’t fully understand how modern cloud systems work, or how millions of users can access massive amounts of services without interruption. What fascinates me most is the elasticity of resource allocation. Think about Netflix: every evening, millions of people connect at the same time to watch their favorite series. This creates a huge traffic peak. Yet, everything runs smoothly without downtime. ...