I'd like to share my open-source project Proxmox-GitOps, a Container Automation Framework for provisioning and orchestrating Linux containers (LXC) on Proxmox VE - encapsulated as a composite Infrastructure as Code (IaC) monorepository.
By encapsulating infrastructure within an extensible monorepository - recursively resolved from Git submodules at runtime - Proxmox-GitOps provides a comprehensive Infrastructure-as-Code (IaC) abstraction for an entire, automated, container-based infrastructure.
Originally, it was a personal attempt to bring industrial automation and cloud patterns to my Proxmox home server. It's designed as a platform architecture for a self-contained, bootstrappable system - a generic IaC abstraction (customize, extend, .. open standards, base package only, .. - you name it ) that automates the entire infrastructure. It was initially driven by the question of what a Proxmox-based GitOps automation could look like and how it could be organized.
I'd like to share my open-source project Proxmox-GitOps, a Container Automation Framework for provisioning and orchestrating Linux containers (LXC) on Proxmox VE - encapsulated as a composite Infrastructure as Code (IaC) monorepository.
Proxmox-GitOps (@Github): https://github.com/stevius10/Proxmox-GitOps
Demo: (~1m): on Github
By encapsulating infrastructure within an extensible monorepository - recursively resolved from Git submodules at runtime - Proxmox-GitOps provides a comprehensive Infrastructure-as-Code (IaC) abstraction for an entire, automated, container-based infrastructure.
Originally, it was a personal attempt to bring industrial automation and cloud patterns to my Proxmox home server. It's designed as a platform architecture for a self-contained, bootstrappable system - a generic IaC abstraction (customize, extend, .. open standards, base package only, .. - you name it ) that automates the entire infrastructure. It was initially driven by the question of what a Proxmox-based GitOps automation could look like and how it could be organized.