How clarknova99/talos-cluster works
High-Level Architecture Components
a) Infrastructure Layer
• Hardware nodes (3x Beelink EQ13, 2x Intel NUC, Synology NAS)
• Network components (Firewalla Gold, Zyxel Switch)
• Power (APC UPS)
b) Platform Layer
• Talos OS (Operating System layer)
• Kubernetes Control Plane (on Beelink nodes)
• Worker Nodes (on NUC systems)
c) Core Services Layer
• Networking: Cilium (CNI and Load Balancer)
• Security: cert-manager, SOPS with age
• DNS/Ingress: external-dns, ingress-nginx
• Storage: OpenEBS, Minio, Rook-Ceph
• Monitoring: Prometheus, Grafana, Fluent-bit
d) Application Layer (Group by namespace)
• Database systems (CloudNative PG, InfluxDB)
• Media services (Plex, Bazarr, etc.)
• Network services (Cloudflared, Echo-server)
• Observability stack
• Default applications
Connection Flow Representation
• External access paths (bold lines)
Specific Implementation Details
Create distinct sections showing:
a) External Access Flow
Internet -> Cloudflare -> Cloudflared -> Ingress-NGINX -> Services
b) Storage Architecture
Applications -> PVC -> OpenEBS/Rook-Ceph -> Physical Storage
c) Monitoring Flow
Metrics -> Prometheus -> Grafana
Logs -> Fluent-bit -> Loki -> Grafana
Key Elements to Highlight
• GitOps workflow with Flux
• Backup paths and storage locations
• Security boundaries and certificate management
• Network policy enforcement points
• High availability configurations
• Persistent storage paths