How belmironeto/homelab works
Project type and purpose
• This is an “infrastructure-as-code” homelab project. It orchestrates virtual machines (via Proxmox), Kubernetes clusters (via K3s), and GitOps (via ArgoCD) using Terraform, a custom Terraform provider, and Ansible playbooks.
File structure
• Top-level:
• ansible_playbooks/ – provisioning & configuration roles for K3s, ArgoCD, ingress, contexts, cluster joins
• terraform_modules/ – reusable Terraform code for Proxmox VMs (k8s_nodes)
• terraform_stack/ – concrete Terraform stacks (k3s_argo, k8s_default) with state and inventory templates
• terraform_provider/ – Go code for a custom “multirouter” Terraform provider
• argocd_platform/ – GitOps config (applicationset) for ArgoCD
• Patterns & config:
• Terraform modules vs. stacks (module reuse vs. environment-level stacks)
• Ansible roles organized by concern (install_k3s, init_master, join_workers, install_argocd, etc.)
• Inventory templating for dynamic host lists
README for additional insights
• Simple summary: “A homelab project with some IaC – Ansible Playbooks, Terraform Modules, Terraform Stack.”