Skip to content

Latest commit

 

History

History
128 lines (83 loc) · 9.32 KB

README.md

File metadata and controls

128 lines (83 loc) · 9.32 KB
Raw

Home Operations

HomeOps repo managed by k8s ☸️

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

Discord   Kubernetes   Renovate

Home-Internet   pre-commit   Alertmanager

Age-Days   Uptime-Days   Node-Count   Pod-Count   CPU-Usage   Memory-Usage   Power-Usage

📖 Overview

Here, I perform DevOps best practices but at home. Check out the hardware section where I describe what sort of hardware I am using. Thanks to Ansible, it's very easy for me to manage my home infrastructure and the cluster. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Terraform, Kubernetes, Flux, Renovate and GitHub Actions.

⛵ Kubernetes

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

Installation

For my cluster, I decided to use the PostgreSQL database instead of high IO load using etcd. I store critical data for my cluster in the PostgreSQL database and maintain it in High Availability mode. I use k3s deployed on ubuntu machines. For that I use ansible to prepare the machines and then install k3s and deploy my cluster configuration.

Core Components

  • cert-manager - SSL certificates - with Cloudflare DNS challenge
  • cillium - CNI for k8s
  • cloudflared: Enables Cloudflare secure access to my ingresses.
  • external-dns: Automatically syncs ingress DNS records to a DNS provider.
  • external-secrets: Managed Kubernetes secrets using 1Password Connect.
  • flux - GitOps tool for deploying manifests from the cluster directory
  • ingress-nginx: Kubernetes ingress controller using NGINX as a reverse proxy and load balancer.
  • k8s_gateway - DNS resolver for all types of external Kubernetes resources
  • kube-vip - layer 2 load balancer for the Kubernetes control plane
  • longhorn - storage class provider for data persistence (yeah I'm giving longhorn second chance)
  • reflector - mirror configmaps or secrets to other Kubernetes namespaces
  • reloader - restart pods when Kubernetes configmap or secret changes
  • sops: Managed secrets for Kubernetes which are commited to Git.
  • spegel: Stateless cluster local OCI registry mirror.
  • system-upgrade-controller - upgrade k3s

☸ GitOps

Flux watches my kubernetes folder (see Directories below) and makes the changes to my cluster based on the YAML manifests.

The way Flux works for me here is it will recursively search the kubernetes/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.

Directories

This Git repository contains the following directories under kubernetes.

📁 kubernetes      # Kubernetes cluster defined as code
├─📁 bootstrap     # Flux installation
├─📁 flux          # Main Flux configuration of repository
└─📁 apps          # Apps deployed into my cluster grouped by namespace (see below)

🗄️ Hardware

My homelab runs on the following hardware (all k8s nodes are running on ubuntu 20.04):

Device OS Disk Size Data Disk Size Ram Purpose
Udoo Bolt V8 AMD Ryzen 250GB NVMe N/A 32GB k3s node
Intel NUC 250GB NVMe 1TB HDD 32GB k3s node
AMD GPU Server 250GB NVMe 1TB SSD 32GB k3s node with Nvidia GPU
TRUENAS ZFS raidz 1 40TB 4x10TB HDD 32GB Storage
Unifi UDM Pro SSD 14GB HDD 1TB 4GB Router and security Gateway
Unifi Switch 16 PoE N/A N/A N/A Switch with 802.3at PoE+ ports
Database Server 20GB N/A 2GB Database for k3s cluster instead of etcd
Offsite Machine 60 GB 8TB 8GB for backups and offsite storage

📰 Blog post

Feel free to checkout my blog axell.dev which is also open source! I also have made a blog post about HW, what were my choices... which ones were good and which ones were bad. Click here.

🤝 Gratitude and Thanks

I am proud to be a member of the home operations (previously k8s-at-home) community! I received a lot of help and inspiration for my Kubernetes cluster from this community which helped a lot. Thanks! ❤️

If you are interested in running your own k8s cluster at home, I highly recommend you to check out the k8s-at-home website.

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

🔏 License

See LINCENSE.