This message was deleted.
# harvester
a
This message was deleted.
a
there is an known issue
1
if you use LB workload type
cluster
instead of `vm`; then check if
kube-vip
is deployed in your guest k8s cluster
it needs such toleration
Copy code
tolerations:
  - effect: NoSchedule
    key: <http://node-role.kubernetes.io/control-plane|node-role.kubernetes.io/control-plane>
    operator: Exists
  - effect: NoExecute
    key: <http://node-role.kubernetes.io/etcd|node-role.kubernetes.io/etcd>
    operator: Exists
and the default one lacks of the second toleration, and thuse no
ip
is alloced as the
kube-vip
is node deployed