Add Proxmox-GitOps #63
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I would like to propose adding my community open-source project, Proxmox-GitOps, to the
Toolssection.Conceptually, this project applies declarative GitOps principles championed by tools like Flux, but targets Proxmox VE and LXC instead of Kubernetes. It uses a self-contained composite monorepo and manages the complete lifecycle of LXC containers via the built-in Git platform.
I believe this is could be valuable because it demonstrates the flexibility of GitOps and provides a solution for automating infrastructure directly on Proxmox, described declaratively as Infrastructure-as-Code.
I think the concept itself, a recursively resolved monorepo, could be interesting as well: Encapsulate infrastructure libraries with which the platform builds itself, creates an operational pattern and working base in recursive scenario, which benefits of the functional programming style resulting in stable and reproducible behaviour.
In line with the contribution guidelines:
Thank you for your consideration!