How anthonyenr1quez/k3s-gitops works
Main Components
a. Infrastructure Layer:
• Three physical nodes (gulsun, loreto, mina) with their specifications
• Network infrastructure (including MetalLB for load balancing)
• Storage systems (NFS, local-path, democratic-csi)
b. Platform Layer:
• K3s Kubernetes distribution
• Flux GitOps engine
• Core services (cert-manager, gateway-api, envoy-gateway)
c. Application Layer (grouped by namespace):
• Download stack (bazarr, prowlarr, qbittorrent, radarr, sonarr, requestrr)
• Media stack (calibre, plex)
• Home automation (home-assistant, mealie)
• Storage services (minio, nfs-server, volsync)
• Networking services (blocky, omada-controller)
• Observability (botkube)
[Physical Infrastructure]
• ↓
[Kubernetes Layer]
• ↓
[Platform Services]
• ↓
[Application Services]
Key Relationships to Highlight
• Flux GitOps workflow:
GitHub → Flux → Kubernetes Resources
• Storage relationships:
NFS Server → PersistentVolumes → Applications
• Network flow:
External Traffic → Envoy Gateway → Services
• Backup paths:
Applications → VolSync → MinIO/External Storage
Specific Implementation Details
a. Create three main sections:
[Infrastructure]
• Show 3 physical nodes
• MetalLB load balancer
• Network storage (11TB NFS)
[Platform Core]
• Flux controllers
• Cert-manager
• Gateway API components
• Storage provisioners
[Applications]
Group by namespace:
• download/
• media/
• home/
• networking/
• storage/
• observability/
b. Special notations for:
• SOPS encrypted secrets
• Persistent storage locations
• External access points
• Backup paths