When provisioning a k3s cluster on top of Harvester 1.5.0; what is the most straightforward way of getting a LoadBalancer working? I tried both kube-vip (causes the nodes' cluster agents to disconnect immediately upon installation of the daemonset) as well as the Harvester Cloud Provider (services of type LoadBalancer did not get any IP address; logs of harvester-cloud-controller pod showed timeouts when trying to access 127.0.0.1:8001)

Hi @abundant-camera-87627! What versions are you using in terms of the underlying Harvester, the external Rancher, and k3s