This message was deleted.
# harvester
a
This message was deleted.
r
That is probably because there’s no harvester-cloud-provider running. Harvester cloud provider is designed to run on the guest cluster. For rancher-vcluster + harvester-baremetal-container-workload combination, it’s not supported. That said, I have a feeling that you can directly leverage kube-vip running on the Harvester cluster to create LB-type services. Just need to craft the manifest to follow the usage of kube-vip.
I just experimented with it and it can achieve the desired effect. However, under this combination, the pool management function will be lost. This means that the IP allocation of the load balancer must be maintained by the user, otherwise, DHCP IPAM must be used.
Simply put, you’ll need to specify the
loadBalancerIP
field in the LB-type service during its creation. Either pick one valid IP address from the pool manually or fill in
0.0.0.0
to let kube-vip run the DHCP client for you.