This message was deleted.

As far as I know the next release 1.2.0 there will have a better integration of the already present kubevip loadbalancer to expose the classic vm workloads via a virtual IP on the VMNetworks. So you just could use regular Networking between diferrent VMNetworks or put the VM-Workloads on the same VMNetworks as your K8S Nodes I guess

great. that’s a good message. It seems that harvester update releases very quickly and frequently. I wonder if it has a smooth and automatical update procedure, i.e. I could update it from 1.1.2 to 1.2.0 with less manual care. Have you encounter any problem in operate harvester cluster. great thanks.

I hope so too xD We will try to update our bare-metal servers as soon aus 1.2 is released and it will be our first upgrade .... so fingers crossed :)

@miniature-lock-53926 that’s why I want my esxi layer to be here. it at least gives me a guarantee for recovery.