Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/martinohmann/home-ops
https://github.com/martinohmann/home-ops
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/martinohmann/home-ops
- Owner: martinohmann
- License: mit
- Created: 2023-11-08T12:19:29.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-04-13T20:44:58.000Z (7 months ago)
- Last Synced: 2024-04-14T01:52:18.623Z (7 months ago)
- Language: YAML
- Size: 3.65 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
### Kubernetes at Home
_... managed with Terraform, Ansible, Flux, Renovate, and GitHub Actions_
[](https://k3s.io/)
[](https://fluxcd.io/)
[](https://github.com/renovatebot/renovate)
[](https://github.com/kashalls/kromgo/)
[](https://github.com/kashalls/kromgo/)
[](https://github.com/kashalls/kromgo/)
[](https://github.com/kashalls/kromgo/)
[](https://github.com/kashalls/kromgo/)
[](https://github.com/kashalls/kromgo/)
---
## 📖 Overview
This is a mono repository for my home infrastructure and Kubernetes cluster. I
try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools
like [Ansible](https://www.ansible.com/),
[Terraform](https://www.terraform.io/), [Kubernetes](https://kubernetes.io/),
[Flux](https://github.com/fluxcd/flux2),
[Renovate](https://github.com/renovatebot/renovate), and [GitHub
Actions](https://github.com/features/actions).
---
## ⛵ Kubernetes
There is a template over at
[onedr0p/flux-cluster-template](https://github.com/onedr0p/flux-cluster-template)
if you want to try and follow along with some of the practices I use here.
### Installation
My cluster is [k3s](https://k3s.io/) provisioned over
[Proxmox](https://www.proxmox.com/) Ubuntu VMs using the
[Ansible](https://www.ansible.com/) galaxy role
[ansible-role-k3s](https://github.com/PyratLabs/ansible-role-k3s). The VMs are
managed via [Terraform](./terraform/proxmox).
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 server for NFS
shares, bulk file storage and backups.
### Core Components
- [actions-runner-controller](https://github.com/actions/actions-runner-controller): self-hosted Github runners
- [cilium](https://github.com/cilium/cilium): internal Kubernetes networking plugin
- [cert-manager](https://cert-manager.io/docs/): creates SSL certificates for services in my cluster
- [external-dns](https://github.com/kubernetes-sigs/external-dns): automatically syncs DNS records from my cluster ingresses to a DNS provider
- [ingress-nginx](https://github.com/kubernetes/ingress-nginx/): ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer
- [longhorn](https://github.com/longhorn/longhorn): distributed block storage for persistent storage
- [sops](https://toolkit.fluxcd.io/guides/mozilla-sops/): managed secrets for Kubernetes, Ansible, and Terraform which are committed to Git
- [system-upgrade-controller](https://github.com/rancher/system-upgrade-controller): automate K3s server and agent updates
- [volsync](https://github.com/backube/volsync): backup and recovery of persistent volume claims
### GitOps
[Flux](https://github.com/fluxcd/flux2) watches the clusters in my
[kubernetes](./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 (`ks.yaml`). Under the control of
those Flux kustomizations there will be a `HelmRelease` or other resources
related to the application which will be applied.
[Renovate](https://github.com/renovatebot/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).
```sh
📁 kubernetes
├── 📁 main # main cluster
│ ├── 📁 apps # applications
│ ├── 📁 bootstrap # bootstrap procedures
│ ├── 📁 flux # core flux configuration
│ └── 📁 templates # re-useable components
└── 📁 storage # storage cluster
├── 📁 apps # applications
├── 📁 bootstrap # bootstrap procedures
└── 📁 flux # core flux configuration
```
---
## 🔧 Hardware
Click to see the rack!
| Device | Count | Disk Size | Ram | Operating System | Purpose |
| ------------------------------ | ----- | ------------------------------------------- | ---- | ---------------- | --------------------------------- |
| ThinkCentre M900 Tiny i5-6500T | 2 | 1TB NVMe | 32GB | Proxmox VE 8 | Kubernetes VMs |
| ThinkCentre M900 Tiny i7-6700T | 1 | 1TB NVMe | 32GB | Proxmox VE 8 | Kubernetes VMs + UniFi Controller |
| STRHIGP Mini J4125 | 1 | 128GB SSD | 8GB | OPNsense | Router |
| Topton N5105 DIY NAS | 1 | 240GB SSD + 2x 6TB HDD ZFS (mirrored vdevs) | 32GB | Debian 12 | NFS + Backup Server |
| PiKVM (Raspberry Pi 4) | 1 | 16GB (SD) | 4GB | PiKVM (Arch) | KVM |
| UniFi USW-24-PoE | 1 | - | - | - | Core Switch |
---
## 🤝 Gratitude and Thanks
Thanks to all the people who donate their time to the [Home
Operations](https://discord.gg/home-operations) Discord community. Be sure to
check out [kubesearch.dev](https://kubesearch.dev/) for ideas on how to deploy
applications or get ideas on what you may deploy.
---
## 📜 Changelog
See my _awful_ [commit history](https://github.com/martinohmann/home-ops/commits/main)
---
## 📜 License
See [LICENSE](./LICENSE)