Default loadbalancer for nginx ingress also targets control plane nodes

[MariusSchiffer]

I have created a fresh cluster with 5 agent nodes and 3 control plane nodes.
Unfortunately, the ingress loadbalancer not only targets the agent nodes, but also the control plane nodes.

Do you have any idea what influences this?

[mysticaltech]

@MariusSchiffer If using Hetzner LB, it shouldn't be case, unless you set allow_scheduling_on_control_plane to true, in which case you need to set it to false.

Now if you use klipperLB instead of the Hetzner one, then it's something expected. For an HA setup like yours, best to use the Hetzner LB.

[mysticaltech]

@MariusSchiffer If it can help, I have a good feeling that this is caused by the default Helm config we give to Nginx. And this can be changed at the bottom of the kube.tf, if you want to read the ingress-nginx helm file doc and play with this, maybe you can make it work it, if so please let us know.

[MariusSchiffer]

Strangely enough, this also happens with traefik. I did upgrade the terraform provider beforehand

[ifeulner]

Hm, nginx is providing it's service via ClusterIP, so isn't that by default available on all nodes? And therefore the load balancer addresses also all nodes? (servers and agents)?

[mysticaltech]

@ifeulner Before at least the LB did not take control planes as targets unless we allowed scheduling on the control plane. However, I will double-check later, to see if I can reproduce the issue.

[mysticaltech]

FYI folks, #447 (comment)