You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to set up a Kubernetes Cluster which has the hcloud-cloud-controller-manager installed. As expected, the hcloud-cloud-controller-manager will try to map my Kubernetes LoadBalancers to a Hetzner LoadBalancer. However, I would like to let MetalLB do that job in my case. Is there any way to prevent hcloud-cloud-controller-manager from grabbing a certain Kubernetes Loadbalancer? How can I define which LoadBalancer should be handled by which controller?
Best regards
Matthias
The text was updated successfully, but these errors were encountered:
I don't think that this is possible. MetalLBs use case is intended for "bare metal clusters" so deploy clusters on bare metal. So i don't think it is possible to have MetalLB and our Load Balancers (or any other Load Balancer). We added a new ENV (HCLOUD_LOAD_BALANCERS_ENABLED) flag to the latest version (will be released officially soon). Therefore you can disable the whole Hetzner Cloud Load Balancers managing.
Hey,
I'm trying to set up a Kubernetes Cluster which has the hcloud-cloud-controller-manager installed. As expected, the hcloud-cloud-controller-manager will try to map my Kubernetes LoadBalancers to a Hetzner LoadBalancer. However, I would like to let MetalLB do that job in my case. Is there any way to prevent hcloud-cloud-controller-manager from grabbing a certain Kubernetes Loadbalancer? How can I define which LoadBalancer should be handled by which controller?
Best regards
Matthias
The text was updated successfully, but these errors were encountered: