Hi,
I‘d like to share my hobby and passion project Proxmox-GitOps, which I think could also be very interesting for other who wants to automate their infrastructure.
Proxmox-GitOps: https://github.com/stevius10/Proxmox-GitOps
Demo (1min+): https://youtu.be/2oXDgbvFCWY
Proxmox-GitOps implements a self-contained GitOps environment for provisioning and orchestrating Linux Containers (LXC) on Proxmox VE.
Encapsulating infrastructure within an extensible monorepository — recursively resolved from Git submodules at runtime — it provides a comprehensive Infrastructure-as-Code (IaC) abstraction for an entire, automated container-based infrastructure.
Core Concepts
- Recursive Self-Management: The control plane executes from within the managed containers to maximize reproducibility and minimize configuration drift.
- Git as Current Desired State: All operations map to standard Git workflows (commit, merge, rollback) in a completely stateless management model.
- Convention-Based Extensibility: * **Convention-Based Extensibility:** Add a new service by copying a container definition from the `libs` directory, adding a minimal cookbook and a `config.env` file. The pipeline automatically handles provisioning, configuration, and validation.
- Loose Coupling: Containers remain independently replaceable and continue to function without requiring manual follow-up actions after changes.
Environment
- Proxmox: 8.4–9.0
- Local bootstrap via Docker
I‘d love to hear your thoughts
I‘d like to share my hobby and passion project Proxmox-GitOps, which I think could also be very interesting for other who wants to automate their infrastructure.
Proxmox-GitOps: https://github.com/stevius10/Proxmox-GitOps
Demo (1min+): https://youtu.be/2oXDgbvFCWY
Proxmox-GitOps implements a self-contained GitOps environment for provisioning and orchestrating Linux Containers (LXC) on Proxmox VE.
Encapsulating infrastructure within an extensible monorepository — recursively resolved from Git submodules at runtime — it provides a comprehensive Infrastructure-as-Code (IaC) abstraction for an entire, automated container-based infrastructure.
Core Concepts
- Recursive Self-Management: The control plane executes from within the managed containers to maximize reproducibility and minimize configuration drift.
- Git as Current Desired State: All operations map to standard Git workflows (commit, merge, rollback) in a completely stateless management model.
- Convention-Based Extensibility: * **Convention-Based Extensibility:** Add a new service by copying a container definition from the `libs` directory, adding a minimal cookbook and a `config.env` file. The pipeline automatically handles provisioning, configuration, and validation.
- Loose Coupling: Containers remain independently replaceable and continue to function without requiring manual follow-up actions after changes.
Environment
- Proxmox: 8.4–9.0
- Local bootstrap via Docker
I‘d love to hear your thoughts
Last edited: