How chaitanya2692/my-homelab works
Project type and purpose
• This is a Kubernetes-based Homelab HTPC (Home Theater PC) system running on k3s.
• It follows a microservices architecture, deploying multiple media-management, download, streaming and utility apps into separate namespaces.
• GitOps and CI/CD play a central role: ArgoCD and GitHub Actions manage deployment and manifest generation.
File structure
• Top-level:
• .github/workflows – CI definitions (push.yml, merge.yml)
• argocd/ – GitOps application definitions
• base/ – Kustomize “base” manifests for htpc, infra, utils namespaces
• overlays/ – environment-specific overlays (staging, production)
• scripts/ – helper scripts (bootstrap, validate, deploy, nuke, update-manifests)
• Within base/: three namespaces:
• htpc/ – Sonarr, Radarr, Transmission, Prowlarr, FlareSolverr, Jellyfin
• infra/ – Traefik, cert-manager, MetalLB, storage (LocalPathProvisioner)
• utils/ – Dashy, Nextcloud, Immich, Tandoor
• Kustomization.yaml files tie these into composable overlays.
• argocd/app contains the ArgoCD Application CRDs to point at these bases/overlays.
Key architecture details from README
• Networking & Ingress: MetalLB (L2 LoadBalancer), Traefik IngressController (IngressRoute CRDs), HTTP→HTTPS, custom middleware.
• Certificate management: cert-manager with Cloudflare DNS-01 for wildcard TLS.
• Storage: host-path PVs + PVCs (htpc-pvc, infra-pvc, utils-pvc) backing media, infra, utility data.
• Workflows: Sonarr/Radarr → Jackett → Transmission → post-processing → Jellyfin.
• CI/CD: GitHub Actions runs yamllint, kubeconform, kustomize; merge pipeline updates install.yaml; ArgoCD syncs cluster.