Using an existing LB in Hetzner Cloud for control plane endpoint

[Stringls]

Hi! Is it possible to use an existing LB in Hetzner Cloud for Control plane? I didn't find any info about that in docs/

controlPlaneLoadBalancer.enabled | bool | true | no | Specifies if a load balancer should be created

If set controlPlaneLoadBalancer.enabled to false, then LB is not created, but I also cannot specify which one cluster should use

[janiskemper]

You have to specify the ControlPlaneEndpoint then!

[janiskemper]

Here it is in the docs
https://github.com/syself/cluster-api-provider-hetzner/blob/main/docs/reference/hetzner-cluster.md#usage-without-hcloud-load-balancer

[Stringls]

@janiskemper Sorry for late reply. So I can create a new LB11 in Hetzner Cloud (the same project where cluster is placed), add a new service 443 -> 6443, specify as an endpoint the IPv4 of the LB and port 443, and Hetzner will add a Control plane machine as a target for this LB. Do I understand it correctly?

[batistein]

In general this is correct only that control-planes won't be added automatically as a target! For the caph controller you have disabled the management of a loadbalancer. So you need to manage the routing to the kubernetes api. Usually this feature is used if you have an own loadbalancer in front or you use a global loadbalancer. Also the controlPlaneEndpoint could be used to specify a DNS name. So you could also use your A-Records for some kind of loadbalancing...

[Stringls]

Cool, thank you for clarification @batistein @janiskemper