So I have rebuilt my Production rack with very little in terms of an actual software plan.
I host mostly docker contained services (Forgejo, Ghost Blog, OpenWebUI, Outline) and I was previously hosting each one in their own Ubuntu Server VM on Proxmox thus defeating the purpose.
So I was going to run a VM on each of these Thinkcentres that worked as a Kubernetes Cluster and then ran everything on that. But that also feels silly since these PCs are already Clustered through Proxmox 9.
I was thinking about using LXC but part of the point of the Kubernetes cluster was to learn a new skill that might be useful in my career and I don't know how this will work with Cloudflared Tunnels which is my preferred means of exposing services to the internet.
I'm willing to take a class or follow a whole bunch of "how-to" videos, but I'm a little frazzled on my options. Any suggestions are welcome.
My issue with mgmt.config is that it bills itself as an api-driven "modern" orchestrator, but as soon as you don't have systemd on clients, it becomes insanely complicated to blast out simple changes.
Mgmt.config also claims to be "easy", but you have to learn MCL's weird syntax, which the issue I have with chef and its use of ruby.
Yes, ansible is relatively simple, but it runs on anything (including being supported on actual arm64) and I daresay that layering roles and modules makes ansible quite powerful.
It's kind of like nagios... Nagios sucks. But it has such a massive library of monitoring tricks and tools that it will be around forever.
You skewer two apps for syntax, but not Ansible's fucking YAML? Dood. I'm building out a layered declarative config at the day-job, and it's just page after page with python's indentation fixation and powershell's bipolar expressions. This is better for you?