My Homelab Repository ❄️

... automated via Flux, Renovate and GitHub Actions 🤖

This is a monorepository is for my home kubernetes clusters. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Terraform, Kubernetes, Flux, Renovate, and GitHub Actions.

The purpose here is to learn k8s, while practicing Gitops.

There is a template over at onedr0p/cluster-template if you want to try and follow along with some of the practices I use here.

My clusters run talos linux immutable kubernetes OS. This is a semi-hyper-converged cluster, workloads and block storage are sharing the same available resources on my nodes while I have a separate NAS server running Unraid withg NFS/SMB shares, bulk file storage and backups.

• actions-runner-controller: self-hosted Github runners
• cilium: internal Kubernetes networking plugin
• cert-manager: creates SSL certificates for services in my cluster
• external-dns: automatically syncs DNS records from my cluster ingresses to a DNS provider
• external-secrets: managed Kubernetes secrets using Bitwarden.
• ingress-nginx: ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer
• longhorn: Cloud native distributed block storage for Kubernetes
• rook-ceph: Cloud native distributed block storage for Kubernetes
• sops: managed secrets for Kubernetes, Ansible, and Terraform which are committed to Git
• spegel: stateless cluster local OCI registry mirror
• tf-controller: additional Flux component used to run Terraform from within a Kubernetes cluster.
• volsync: backup and recovery of persistent volume claims

Flux watches the clusters in my kubernetes folder (see Directories below) and makes the changes to my clusters based on the state of my Git repository.

The way Flux works for me here is it will recursively search the kubernetes/${cluster}/apps folder until it finds the most top level kustomization.yaml per directory and then apply all the resources listed in it. That aforementioned kustomization.yaml will generally only have a namespace resource and one or many Flux kustomizations. Those Flux kustomizations will generally have a HelmRelease or other resources related to the application underneath it which will be applied.

Renovate watches my entire repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged Flux applies the changes to my cluster.

This Git repository contains the following directories under Kubernetes.

📁 kubernetes
├── 📁 main               # main cluster
│   ├── 📁 apps           # applications
│   ├── 📁 bootstrap      # bootstrap procedures
│   ├── 📁 flux           # core flux configuration
│   └── 📁 templates      # re-useable components
└── 📁 utility            # utility cluster
    ├── 📁 apps           # applications
    ├── 📁 bootstrap      # bootstrap procedures
    ├── 📁 flux           # core flux configuration
    └── 📁 templates      # re-useable components

Click to see a high-level network diagram

While most of my infrastructure and workloads are self-hosted I do rely upon the cloud for certain key parts of my setup. This saves me from having to worry about two things. (1) Dealing with chicken/egg scenarios and (2) services I critically need whether my cluster is online or not.

The alternative solution to these two problems would be to host a Kubernetes cluster in the cloud and deploy applications like HCVault, Vaultwarden, ntfy, and Gatus. However, maintaining another cluster and monitoring another group of workloads is a lot more time and effort than I am willing to put in.

In my cluster external-dns is deployed with the RFC2136 provider which syncs DNS records to unifi via external-dns-unifi-webhook.

Outside the external-dns instance mentioned above another instance is deployed in my cluster and configured to sync DNS records to Cloudflare. The only ingress this external-dns instance looks at to gather DNS records to put in Cloudflare are ones that have an ingress class name of external and contain an ingress annotation external-dns.alpha.kubernetes.io/target.

Total CPU: 76 threads Total RAM: 384GB

Total CPU: 16 threads Total RAM: 32GB

Big shout out to original cluster-template, and the Home Operations Discord community.

Be sure to check out kubesearch.dev for ideas on how to deploy applications or get ideas on what you may deploy.

See my awful commit history

See LICENSE