This repository contains everything I use to maintain the devices and clusters in my home, along with application deployment into my kubernetes cluster. For more details, see the readme's in each folder. .
- Apps YAML files for configuration and deployment off applications into kubernetes
I try to run everything bare metal with virtual machines (running on Proxmox).
| Device | Count | Storage | Purpose |
|---|---|---|---|
| HP MicroServer | 1 | 12TB RAID Z1 | Media and backup storage |
| Intel NUC8i3BEH | 1 | 500GB SSD + 120GB NVMe | Proxmox VM host one |
| BeeLink SER3 | 1 | 500GB SSD + 120GB NVMe | Proxmox VM host Two |
- Infrastructure:
A. Virtual machines run ubuntu 22.04. B. K3S cluster consists of 3 Master nodes and 2 worker nodes. C. Block storage for Nodes is handled by Longhorn. D. Application deployment is handled by Flux.
Secrets and configmaps with private data are encrypted with sops where only myself and flux can read said secrets.
Code linting is performed by Super-Linter. Application YAML is also check and validated by Datree
Flux and kustomize recursively look through the folder structure in clusters/prod for kustomization.yaml files. The top level file in the Apps subfolder tells kustomize to look at certain ks.yaml files or further subfolder. Ks.yaml is used when we need to tell kustomize to either do a health check when deploying or set dependencies so that resources deploy in the correct order E.G We don't want to deploy something that needs persistent storage without having Longhorn online, otherwise PVC's will fail to create.
- apps-kustomization.yaml - Tells kustomize to watch the folderstructure and also decrypt files when they are encrypted with sops.
- global-kustomization.yaml - Tells flux to bring in files in the config folder Where further things like Secrets and variables are kept / injected into the cluster at kustomization build time.
I learned a lot from the people over @ Awesome-home-kubernetes and from the k8s@home discord channel.