How bartbrinkman/homelab-k8s works
High-Level Components
a. Infrastructure Layer
• Kubernetes Cluster (kubeadm-based)
• Flannel Network (pod-network-cidr: 10.244.0.0/16)
• Control Plane Components
b. Core Platform Services
• Argo CD (Central GitOps Controller)
• App-of-Apps Root Application
• Ingress-NGINX Controller
• Cert-Manager
• Sealed Secrets
c. Monitoring & Observability Stack
• Kube-Prometheus Stack
• Metrics Server
• Istio with Kiali
• InfluxDB
d. Storage & Data Services
• Longhorn (Storage)
• MinIO with DirectPV
• MySQL
• PostgreSQL
e. Application Services
• Multiple web applications (BudgetZero, CyberChef, Grocy, etc.)
• Development Tools (Code-Server)
• Infrastructure Management (Portainer, Kubernetes Dashboard)
Connection Flows
Key relationships:
• Argo CD's control flow to all applications
• Ingress traffic flow through OAuth2-Proxy
• Storage relationships between apps and persistent volumes
• Monitoring data flow to Prometheus
• Service mesh connections through Istio
Specific Implementation Details
Crucial elements:
• KEDA scalers (shown for Grocy, Kubernetes Dashboard, etc.)
• Cert-Manager integration with ingress resources
• Sealed Secrets usage for sensitive data
• DirectPV integration with MinIO
Hierarchy Levels
1. Infrastructure Foundation (Bottom)
2. Core Services (Next Layer)
3. Platform Services (Middle Layer)
4. Applications (Top Layer)