Skip to content
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

Ingress is going on all the nodes #10436

Closed
simonfoilen opened this issue Jun 29, 2024 · 1 comment
Closed

Ingress is going on all the nodes #10436

simonfoilen opened this issue Jun 29, 2024 · 1 comment

Comments

@simonfoilen
Copy link

#10434 was closed before being fully resolved. I cannot reopen it and it seems noone will follow up since it is closed and marked done, so I am opening a new issue...

I downloaded K3S's code and it looks like the problem is that the k3s code is only selecting nodes for LoadBalancer
and if we check the "traefik" service that k3s installs, its LoadBalancer part doesn't have a svccontroller.k3s.cattle.io/lbpool (so it picks all nodes).

So, in other words, that cannot work and that is not the behavior we are expecting. Even the person that replied to the other issue pointed to the documentation saying that it should work.

It seems I would need to:

  • disable traefik
  • install traefik myself with
    • 2 services:
      • traefik-tor1_1 : with svccontroller.k3s.cattle.io/lbpool=tor1_1
      • traefik-fra1_1 : with svccontroller.k3s.cattle.io/lbpool=fra1_1
    • 2 Ingress classes
      • traefik-tor1_1
      • traefik-fra1_1
  • Then, I will be able to set on my Ingress the ingressClassName for the right load-balancer pool to use.

You might consider automatically doing that. For instance, when svccontroller.k3s.cattle.io/enablelb=true, you could split traefik like that.
What do you think?

@brandond
Copy link
Member

it seems noone will follow up since it is closed and marked done

Please don't open a new issue, keep discussion on that one. No one is responding because it's the weekend and we (generally speaking) have other things to do with our lives outside working hours.

@k3s-io k3s-io locked and limited conversation to collaborators Jun 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants