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
Before now, I've always disabled the built in cloud controller manager that comes bundled with k3s.
But today I decided to leave it enabled as it is and created a service of type load balancer only to discover something strange.
While, my gateway controller traefik is deployed as kind:Deployment with a replica of just 1 I noticed that ServiceLb seems to be running as a DaemonSet as shown below:
Before now, I've always disabled the built in cloud controller manager that comes bundled with k3s.
But today I decided to leave it enabled as it is and created a service of type load balancer only to discover something strange.
While, my gateway controller traefik is deployed as
kind:Deployment
with a replica of just 1 I noticed that ServiceLb seems to be running as a DaemonSet as shown below:That leaves me with the question, which IP do I then create an A record for in my DNS settings for routing? All 5 IPs?
Is there no way to work with just a single IP, because I can imagine this scaling even more if I add an extra node to the cluster
The text was updated successfully, but these errors were encountered: