Architecture
System design for the fzymgc-house cluster: the infrastructure layers, how the components connect, and the reasoning behind the main technical choices.
In this section
Section titled “In this section”- System Overview: the layers, the hardware, and how traffic, secrets and identity flow
- Architecture Decisions: the decision records behind significant choices
Three layers
Section titled “Three layers”graph TB
subgraph Layer1[Layer 1: Ansible]
A[Node configuration]
B[k3s]
C[Cilium]
end
subgraph Layer2[Layer 2: Terraform]
D[Vault]
E[Keycloak]
F[Cloudflare, DNS, Tailscale]
end
subgraph Layer3[Layer 3: ArgoCD]
G[Application manifests]
H[GitOps sync]
end
Layer1 --> Layer2 --> Layer3
| Layer | Tool | Purpose |
|---|---|---|
| 1 | Ansible | Node configuration, k3s, the CNI, the resolver pair, heimdall and the NAS |
| 2 | Terraform | Vault, Keycloak, Cloudflare, DNS records, Tailscale, UniFi and other infrastructure |
| 3 | ArgoCD | Every Kubernetes application, synced from main |
Hardware
Section titled “Hardware”- Two Turing Pi 2 boards, alpha and beta
- Eight RK1 compute modules: three control plane nodes and five workers
- Armbian on every node
- Cilium as the CNI, with Hubble, and the API server VIP announced over BGP