Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to know which IP to pick from Servicelb #11143

Closed
wanclem opened this issue Oct 21, 2024 · 0 comments
Closed

How to know which IP to pick from Servicelb #11143

wanclem opened this issue Oct 21, 2024 · 0 comments

Comments

@wanclem
Copy link

wanclem commented Oct 21, 2024

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:

kube-system    svclb-traefik-64427955-2p27k               2/2     Running   0               2m46s
kube-system    svclb-traefik-64427955-grl9s               2/2     Running   0               2m47s
kube-system    svclb-traefik-64427955-xzdz9               2/2     Running   0               2m47s
kube-system    svclb-traefik-64427955-xzrcw               2/2     Running   0               2m47s
kube-system    svclb-traefik-64427955-zjgcd               2/2     Running   0               2m46s

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

@wanclem wanclem changed the title How to know which ip to pick from Servicelb How to know which IP to pick from Servicelb Oct 21, 2024
@k3s-io k3s-io locked and limited conversation to collaborators Oct 21, 2024
@brandond brandond converted this issue into discussion #11144 Oct 21, 2024
@github-project-automation github-project-automation bot moved this from New to Done Issue in K3s Development Oct 21, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

1 participant