You can have replication if you have Starwind Clustering on the hosts (That's how I have some customers). That said, even on those situations I have a DC on the Local Host Hyperv of one of the servers or have a Site to Site VPN with a DC on Azure or AWS as a failsafe.
Podman is not Kubernetes. Also when you install Kubernetes you don't get a podman1 service (or any type of podman service).
When you install Kubernetes that way you don't get a Kubernetes service. You seemingly have to start the kube-proxy, kube-scheduler, kube-controller-manager, kube-api-server, and the kubelet separately.
It installs docker, which is deprecated in k8s now. They have switched to using containerd which is pretty much the standard runtime now.
So I'll stick with my original recommendation.
Yep, this is why I need to mess with this stuff in my home lab. I can't even talk about it intelligently yet!
So, because Veeam reapplied the old snapshot, everything between then and now was lost.
If I keep the old snaphot as current, all the systems have domain trust failure.
I have a backup and there is only a single shared folder on here that will need restored.
Because this site is only 20 Windows computers, and I wanted to stop wasting time after 2 hours, I went brute force.
I disjoined everything from the domain and rejoined them.
With that resolved, I restored the C:\shares folder on the DC from the last Veeam backup.
Site is now working again.
Veeam's replication is now also in the correct state to fall back the replica to the main hyper-v server.
Not fucking touching that tonight.. I R DUN.
Edit: Maybe not the perfectly correct answer, but the answer I went with.