How qjoly/gitops works
Main System Components
a) Cluster Management Layer
• Omni (self-hosted) at the top level
• Connections to multiple Kubernetes clusters (Cortado, Arabica, Lungo, Home)
• Talos OS as the underlying system for nodes
b) Core Infrastructure Layer (Per Cluster)
• CNI: Cilium (with load balancing in ARP mode)
• Storage: Longhorn/ZFS + Local-Path-Provisioner
• Network: Cloudflare Tunnels (specifically for home cluster)
c) Platform Services Layer
• GitOps: ArgoCD
• Ingress: Nginx Ingress Controller/Istio
• Certificate Management: Cert-Manager
• Secret Management:
• Vault (central store)
• External Secrets Operator
• ~~Reflector~~ (noted as removed)
┌─ Omni Control Plane ─────────────────────┐
• ┌─ Cluster Management ──┐ │
• SSO Integration │ │
• Node Management │ │
• ┘ │
• ┬───────────────────────────┘
• ▼
┌─────────────────────────────────────────┐
• Kubernetes Clusters │
• ┬─────────┬─────────┬──────────┤
• Cortado │ Arabica │ Lungo │ Home │
• (OVH) │ (OVH) │ (VM) │ (Local) │
• ┴─────────┴─────────┴──────────┘
Component Relationships
Key relationships:
• ArgoCD → Git Repository (GitOps workflow)
• External DNS → Cloudflare
• Cert-Manager → Let's Encrypt
• Applications → Persistent Storage
• Ingress → External Access
Metadata Section
• Kubernetes versions
• Talos versions
• Cluster ages and uptimes
• Resource usage metrics
Remember to:
• Keep components grouped by function
• Clear data flow directions
• High-availability configurations
• Backup paths and storage relationships
• Monitoring components (Prometheus, Grafana)
This structure reflects the project's sophisticated multi-cluster architecture while maintaining clarity about how components interact across the system.