The GitOps approach definitely has its advantages but for something as simple as a setting as you describe, a round-trip to git makes negative sense when it could've been done directly in a local database.

How have you found the stability of KubeVirt through all of this? Are you using KubeVirt directly or a wrapper? We tried Harvester and it is amazing on day 1. Day 2 is a horrid nightmare of broken upgrade timesink. Granted we started at Harvester 1.4.0 in 2024 but have a couple clusters stuck on 1.5.0 right now and have VM failures regularly. Longhorn was also in use for VM disks and it was horrendously unstable even with dedicated 2x100Gb for each node.

We've moved everything to Proxmox+NetApp now and it's rock solid. Dedicated NICs + switches for corosync since that was the cause of an outage once.