Skip to content

Ansible

From Proxmox to Kubernetes - Evolving My Homelab (part 3)

This is part 3 of my series detailing a transition of my Homelab architecture to using Kubernetes with Proxmox. You can check out the previous parts here:

In part 3, I’ll explore my implementation strategy for Kubernetes and how it has transformed my homelab.

The Strategic Shift to Kubernetes

Kubernetes has become the logical next step for my homelab. I've pointed this out briefly in parts 1 and 2. I enjoy the break-and-fix cycle of learning in my homelab. However, over the years I have found more joy with making things work consistently, from the very start, every time.

From Proxmox to Kubernetes - Evolving My Homelab (part 2)

This is part 2 of my series detailing a transition of my Homelab architecture to using Kubernetes with Proxmox. You can check out part one here: From Proxmox to Kubernetes - Evolving My Homelab (part 1)

In this post, I continue my journey evolving my homelab from a simple Proxmox setup to a more robust Kubernetes-based architecture. Building on part one, I’ll share what worked, what didn’t, and how my approach to self-hosting and automation has changed over time.

From Proxmox to Kubernetes - Evolving My Homelab (part 1)

Introduction & Current Setup Overview

So I've been tinkering with Kubernetes in my homelab for some time now. It's been more of a fun experiment, however, things really started to click for me with how much I enjoyed the declarative orchestration posibilities. Kubernetes os known for container orchestration, and it does allow both imperative and declarative management.

Well, I've already been doing imperative management across my whole homelab with my Proxmox setups, VMs, LXCs, and containers within VMs. So I knew what that required. It's a great way to learn, and truly helps with building a strong problem solving mentality because you are making the configuration update and see the immediate results of your change. So when things break, you can just review what you had just done and learn why it happened and how to resolve it.

Automating resilient backups in my homelab with Ansible and Paperless-ngx

As my data consumption and storage needs grow - both at work and at home - reliable automation becomes non-negotiable. Over the past week, I have invested much needed time to my homelab_ansible GitHub repository; focusing on crafing a robust backup playbook for my paperless-ngx deployment. My goal? A backup workflow I trust to safeguard my documents, regardless of infrastructure or underlying OS.