Show HN: Proxmox-GitOps: Container Automation Metaframework (Recursive Monorepo)(github.com)
github.com
Show HN: Proxmox-GitOps: Container Automation Metaframework (Recursive Monorepo)
https://github.com/stevius10/Proxmox-GitOps
2 comments
Wow, this looks amazing - have to give it a try!
PS: Might want to post this to /r/homelab and /r/proxmox - I'm sure the people there will love this!
PS: Might want to post this to /r/homelab and /r/proxmox - I'm sure the people there will love this!
I'd like to share my open-source project Proxmox-GitOps, a Container Automation platform for provisioning and orchestrating Linux containers (LXC) on Proxmox VE - encapsulated as comprehensive Infrastructure as Code (IaC).
TL;DR: 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.
Core Concepts:
- Recursive Self-management: Control plane seeds itself by pushing its monorepository onto a locally bootstrapped instance, triggering a pipeline that recursively provisions the control plane onto PVE.
- Monorepository: Centralizes infrastructure as comprehensive IaC artifact (for mirroring, like the project itself on Github) using submodules for modular composition.
- Single Source of Truth: Git represents the desired infrastructure state.
- Loose coupling: Containers are decoupled from the control plane, enabling runtime replacement and independent operation.
It's a noncommercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like?
I'd love to hear your thoughts!
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.
Core Concepts:
- Recursive Self-management: Control plane seeds itself by pushing its monorepository onto a locally bootstrapped instance, triggering a pipeline that recursively provisions the control plane onto PVE.
- Monorepository: Centralizes infrastructure as comprehensive IaC artifact (for mirroring, like the project itself on Github) using submodules for modular composition.
- Single Source of Truth: Git represents the desired infrastructure state.
- Loose coupling: Containers are decoupled from the control plane, enabling runtime replacement and independent operation.
It's a noncommercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like?
I'd love to hear your thoughts!
TL;DR: 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.
Core Concepts:
- Recursive Self-management: Control plane seeds itself by pushing its monorepository onto a locally bootstrapped instance, triggering a pipeline that recursively provisions the control plane onto PVE.
- Monorepository: Centralizes infrastructure as comprehensive IaC artifact (for mirroring, like the project itself on Github) using submodules for modular composition.
- Single Source of Truth: Git represents the desired infrastructure state.
- Loose coupling: Containers are decoupled from the control plane, enabling runtime replacement and independent operation.
It's a noncommercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like?
I'd love to hear your thoughts!