← return to posts

Automate from day one with FluxCD

I finally finished filling out my mini racks and migrated my homelab to Kubernetes. I followed a similar setup to this amazing guide: https://k3s.guide/

One of the things I was really grateful for in this experience was how much having FluxCD from day one helped me and saved me so much time. I know a lot of people find ArgoCD difficult and daunting to set up, but FluxCD is much simpler and feels more suitable for homelab needs.

One of the main problems with homelabbing is not remembering what command you ran or what config change actually fixed something. Forcing myself to use GitOps solved this issue.

Here are some reasons I think you should use FluxCD on your homelab (and probably at work) from day one if you’re building a new cluster:

  1. Push and forget – I never have to wonder if I triggered a deploy or not

  2. No extra dependencies – FluxCD only needs Kubernetes, no secrets for GitHub Actions

  3. Discipline – Make intentional code changes instead of getting lost in CLI or click-ops

  4. Simple deployments – Some homelab services can be deployed directly as Kubernetes objects

  5. Easy rebuilds – Sleep easy knowing you can rebuild the entire cluster

Ditch Argo, go Flux.