Check out libvirtd based stacks, because that's what's supported by upstream Linux.
Some shops here migrate to proxmox as a UI because of certification requirements, but I migrated some of my customers to cockpit dashboard, and some to kubernetes. It's always a matter of scale and provisioning requirements.
Cockpit is my favorite so far because it's easy to setup, but its focus isn't cluster scale, which is what most larger companies need. You have to setup basically two cockpit variants: the webui and lots of cockpit server daemons (aka libvirtd on remote machines). The webui then uses SSH to login to other machines to manage them (e.g. via the known_hosts file on the webui server). [3]
Proxmox is pretty old and Perl, but it's doable. Usually storage clustering is a bit painful because you need something on a filesystem layer like ceph clusters.
There's also openshift but no idea if that is an IBM/RedHat lock-in as well, so the SMEs didn't want that risk.
Some shops here migrate to proxmox as a UI because of certification requirements, but I migrated some of my customers to cockpit dashboard, and some to kubernetes. It's always a matter of scale and provisioning requirements.
Cockpit is my favorite so far because it's easy to setup, but its focus isn't cluster scale, which is what most larger companies need. You have to setup basically two cockpit variants: the webui and lots of cockpit server daemons (aka libvirtd on remote machines). The webui then uses SSH to login to other machines to manage them (e.g. via the known_hosts file on the webui server). [3]
Proxmox is pretty old and Perl, but it's doable. Usually storage clustering is a bit painful because you need something on a filesystem layer like ceph clusters.
There's also openshift but no idea if that is an IBM/RedHat lock-in as well, so the SMEs didn't want that risk.
[1] https://cockpit-project.org/
[2] https://www.proxmox.com/en/
[3] https://cockpit-project.org/guide/latest/feature-machines.ht...