How mitchross/k3s-argocd-starter works
Project type and purpose
• This is a GitOps-based Kubernetes starter kit. It defines a production-ready K3s cluster layout, bootstraps Argo CD, installs networking (Cilium, Cloudflared, Gateway API), storage (OpenEBS, NFS CSI), certificate management, a monitoring stack (Prometheus, Grafana, AlertManager) and a set of user applications.
• Its goal: demonstrate a two-level Argo CD ApplicationSet structure (Infrastructure vs. Applications vs. Monitoring) with best practices for security boundaries, sync ordering, self-healing and RBAC.
File structure
• Top-level directories
– infrastructure: YAML manifests split into controllers (Argo CD, cert-manager), networking (cilium, cloudflared, gateway), storage (OpenEBS, CSI-NFS)
– monitoring: manifests for the Prometheus operator stack, Grafana, AlertManager, NodeExporter
– my-apps: per-application overlays (headlamp, nginx, searxng, proxitok, etc.), plus an applications-ApplicationSet manifest
– docs: auxiliary guides (e.g., AdGuard Home DNS)
– .github, .vscode: CI/configuration
• Key files
– infrastructure/infrastructure-components-appset.yaml
– monitoring/monitoring-components-appset.yaml
– my-apps/myapplications-appset.yaml
– infrastructure/controllers/argocd/* (bootstrap of Argo CD itself)
• Patterns
– GitOps (Argo CD) with ApplicationSets grouped into logical projects
– Kustomize overlays per folder
– Helm values injected via Kustomize
– Clear three-tier separation: Infrastructure, Monitoring, User Applications
README for additional insights
– Three Argo CD Projects (Infrastructure, Applications, Monitoring)
– Under Infrastructure: Networking (Cilium, Cloudflared, Gateway), Storage (OpenEBS), Controllers (Cert-Manager)
– Under Monitoring: Prometheus, Grafana, AlertManager, NodeExporter
– Under User Applications: categories (Privacy Apps, Web Apps, Other Apps) and example micro-services
• Details on sync waves, RBAC enforcement, self-healing, prerequisites, and step-by-step quick-start commands