Using *HA* Kubernetes at home, was never so simple!


    Set up a Kubernetes HA Cluster at Home is easy with K3s! In this video I show you what you need to do that and how I’ve used K3s to set up a High Available Kubernetes Cluster in my Home Lab on Proxmox. We also cover an awesome free and open-source tool called Datree, and how to use it to check Kubernetes Deployments for misconfigurations and HA capability.

    Learn Kubernetes:

    Sophos XGS Setup:

    Datree Docs-*:

    Support me and get early access to upcoming videos:

    Follow me:



    00:00 – Introduction
    01:21 – What is K3s?
    02:47 – Getting started with K3s
    04:37 – K3s HA Setups and embedded Etcd
    08:34 – My preferred Setup on Proxmox
    10:30 – Install K3s on the Servers
    14:55 – Set up a Load Balancing
    19:20 – Connect to Kubernetes
    20:36 – Deploy Manifests with Datree-* for HA
    26:18 – Set up Traefik on K3s
    28:27 – Test HA by taking a server down

    #Kubernetes #k3s #homelab

    All links with “*” are affiliate links.


    Previous articleDevOps Tutorial For Beginners in Hindi | What is DevOps in Hindi | DevOps Training | Edureka
    Next articleDOCKER desde CERO a EXPERTO [CURSO COMPLETO en 2 horas] 🐳


    1. This may be off topic, but I've been interested in exposing some web apps that I'm hosting on my home network to the internet. I'm a software engineer, but I don't have a lot of experience in infrastructure. Is there any reasonably safe way to expose servers to the internet? Could anyone recommend any learning materials on how to properly setup IT infrastructure?

      I've always been interested in setting up my homelab properly. Maybe using some combo of Ansible, Kubernetes, maybe some private code repositories and setting up a CICD pipeline locally. This is a very large endeavor and the sheer scale and lack of Infrastructure knowledge on my part makes me hesitant to even try.

      It's also discouraging to me as a beginner that all the existing tutorials out there are either outdated, don't work, or skip difficult topics.

    2. The Achilles heel of any clustering system is the storage. If your services require storage, k8s doesn't really handle that well unless you integrate a clustered file system. This is usually ignored by "How to do k8s cluster" guides. If your services don't require storage or you already have an HA storage setup, then k8s out of the box is great.
      You can also mix ARM (Raspberry PI) and X86 systems, but you'll find that the workloads need to be properly labeled because there aren't pre-created ARM docker containers for all services that you might want to run.