Skip to content

Infrastructure Lab Docs

ADR-007 Infrastructure as Code for Proxmox

Infrastructure Lab Docs

Home
Phase 1: Local
Phase 1: Local
- Admin Box
- ADR-001 Hardening Script
Phase 2: Cloud
Phase 2: Cloud
- Network Architecture
- ClickOps Deployment
Phase 3: Containerization
Phase 3: Containerization
- CI/CD Pipeline
- ADR-004 Workload Architecture
Phase 4: Infrastructure as Code (IaC)
Phase 4: Infrastructure as Code (IaC)
- Infrastructure as Code
- ADR-005 Managed Database
Phase 5: Orchestration
Phase 5: Orchestration
- ADR-006 Lightweight Kubernetes (K3s) on Proxmox VM
- K3s Architecture on Proxmox VM
- ADR-007 Infrastructure as Code for Proxmox ADR-007 Infrastructure as Code for Proxmox
  Table of contents
- Kubernetes
Phase 6: Persistence
Phase 6: Persistence
- ADR-008 Local NVMe Persistence
- Redis & Disaster Recovery
Phase 7: Ingress
Phase 7: Ingress
Phase 8: Package Management
Phase 8: Package Management
- ADR-011 Helm Packaging
- ADR-012 Redis Helm Chart

ADR 007: Infrastructure as Code for Proxmox

Context

We need to provision a Debian VM for K3s on our Proxmox host.

Decision

We will use OpenTofu with the bpg/proxmox provider to declaratively provision the K3s Virtual Machine.

Consequences

Positive: Complete reproducibility. The VM configuration (CPU, RAM, network) is version-controlled and peer-reviewed. We avoid "configuration drift" in our homelab.
Negative: Requires initial setup of Proxmox API tokens and an underlying Cloud-Init template.