Ingress is going on all the nodes about k3s

[brandond]

The ingress is exposed via a loadbalancer. the default loadbalancer for k3s is servicelb, which is documented here: https://docs.k3s.io/networking/networking-services#service-load-balancer

The docs cover limiting which nodes the loadbalancer uses.

[simonfoilen]

yes that is the documentation I said I was following.

I tried putting the labels everywhere without success (as I explained)

I have no clue what is missing right now. So, there is one problem:

• documentation is imcomplete/unclear
• documentation has a bug
• or the implementation has a bug

Could you give me some pointers if that is just a documentation issue?

thanks

[simonfoilen]

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.

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]

if we check the "traefik" service that k3s installs, its LoadBalancer part doesn't have a svccontroller.k3s.cattle.io/lbpool

It is easy enough to do that for yourself, if that's something you want. Most people don't.

If you just wanted the ingress to only use a single node, you could just only label that node with svccontroller.k3s.cattle.io/enablelb=true and do nothing else; nodes that don't have that label will not be used for servicelb.

If you want more fine grained control, you could:

1. Label the node you want the ingress to use with svccontroller.k3s.cattle.io/lbpool=traefik and svccontroller.k3s.cattle.io/enablelb=true
2. Add a HelmChartConfig to add this same label to the traefik service, as described at https://docs.k3s.io/helm#customizing-packaged-components-with-helmchartconfig

   apiVersion: helm.cattle.io/v1
   kind: HelmChartConfig
   metadata:
     name: traefik
     namespace: kube-system
   spec:
     valuesContent: |-
       service:
         labels:
           svccontroller.k3s.cattle.io/lbpool: traefik

If you want to be able to use different ingress classes for different nodes then yes, that will take much more customization and likely multiple installations of the traefik ingress controller, each bound to its own service and lbpool.