A personal homelab infrastructure managed through GitOps principles using Flux CD. This repository contains my ongoing configuration for a Kubernetes-based homelab running media services, cloud storage, and monitoring.

🏗️ Work in Progress: Personal homelab setup that's constantly evolving and being improved.

• Homarr - Customizable homepage and dashboard for homelab services

• Nextcloud - Self-hosted cloud storage, file sync, and collaboration platform
• Immich - High-performance photo and video backup solution (Google Photos alternative)

• Linkding - Self-hosted bookmark manager with full-text search

• Jellyfin - Media server for streaming movies, TV shows, and music
• Jellyfin Vue - Modern web client for Jellyfin
• Sonarr - TV series collection manager with automatic downloading
• Radarr - Movie collection manager with automatic downloading
• Prowlarr - Indexer manager for *Arr applications
• Jackett - API support for torrent trackers
• qBittorrent - BitTorrent client with web interface
• NZBGet - Usenet downloader

• pgAdmin - Web-based PostgreSQL administration tool

homelab/
├── apps/                    # Application definitions
│   ├── base/               # Base configurations
│   └── production/         # Production overlays
├── infrastructure/         # Platform components
│   ├── controllers/        # Infrastructure controllers
│   └── configs/           # Infrastructure configurations
├── monitoring/            # Observability stack
│   ├── controllers/        # Monitoring controllers
│   └── configs/           # Monitoring configurations
├── clusters/              # Cluster configurations
│   └── homelab/          # Main cluster config
└── renovate.json         # Dependency automation

graph TB
    CLIENT["kubectl client"]
    
    subgraph "Proxmox Host p1"
        LB1["K3S-LB01<br/>1C/2GB"]
        SRV1["K3S-SRV01<br/>6C/6GB<br/>server"]
    end
    
    subgraph "Proxmox Host p2"
        LB2["K3S-LB02<br/>1C/2GB"]
        SRV2["K3S-SRV02<br/>6C/6GB<br/>server"]
    end

    subgraph "Ubuntu bare metal"
        SRV3["K3S-SRV03<br/>4C/4GB<br/>server"]
    end
    
    CLIENT --> LB1
    CLIENT --> LB2
    LB1 --> SRV1
    LB1 --> SRV2
    LB1 --> SRV3
    LB2 --> SRV1
    LB2 --> SRV2
    LB2 --> SRV3

    style CLIENT fill:#e3f2fd
    style LB1 fill:#fff3e0
    style LB2 fill:#fff3e0
    style SRV1 fill:#e8f5e8
    style SRV2 fill:#e8f5e8
    style SRV3 fill:#e8f5e8

Flux CD orchestrates the deployment in a layered approach with proper dependencies:

graph TD
    A[🚀 infrastructure-controllers<br/>Longhorn, cert-manager, CloudNative-PG] 
    B[⚙️ infrastructure-configs<br/>Storage Classes, Node Config, Cluster Issuers]
    C[📊 monitoring-controllers<br/>Prometheus, Grafana]
    D[📈 monitoring-configs<br/>Dashboards, Alerts, Ingress]
    E[🔧 apps<br/>Nextcloud, Media Stack, pgAdmin]

    A --> B
    B --> C
    B --> E
    C --> D

    style A fill:#e1f5fe
    style B fill:#f3e5f5
    style C fill:#fff3e0
    style D fill:#fff8e1
    style E fill:#e8f5e8

• Automated backups to Backblaze B2
• Daily (7-day retention) + Weekly (4-week retention) + Monthly (6-month retention)
• Snapshot cleanup daily (7-day retention)

• Continuous WAL streaming with gzip compression to Backblaze B2
• Weekly complet backup.

terraform apply

ansible-playbook k3s.orchestration.site -i inventory.yml

flux bootstrap github \
  --token-auth \
  --owner=Justin-De-Sio \
  --repository=ssh://[email protected]/Justin-De-Sio/homelab\
  --branch=main \
  --path=clusters/homelab \
  --personal

kubectl create secret generic sops-age \
  --namespace=flux-system \
  --from-literal=age.agekey="${SOPS_AGE_KEY}"