How can inbound traffic be routed exclusively to the current node's Traefik pod? about klipper-lb

[au2001]

I want to achieve: when traffic passes through node1 or node2, I want the Traefik on the current node to exclusively handle inbound traffic on that node, rather than on other nodes (if there is no Traefik pod scheduled to the current node, the request should result in an error).

So... no load balancing at all?
What you want is a Service of kind NodePort to expose Traefik directly

[Arc-2023]

I want to achieve: when traffic passes through node1 or node2, I want the Traefik on the current node to exclusively handle inbound traffic on that node, rather than on other nodes (if there is no Traefik pod scheduled to the current node, the request should result in an error).

So... no load balancing at all? What you want is a Service of kind NodePort to expose Traefik directly

well, it's not a convinent way to use node port to expose traefik's service.
to this problem, using the giving configuration can make an effect:

externaltrafficpolicy: Cluster
internaltrafficpolicy: Local

from now on, the traffic is only taken by local traefik pod , load balancing is handled by traefik, not serviceLB

i wonder why externaltrafficpolicy should be false, and why does this truth value affect the behavior of internal traffic policy: even if the internal traffic policy is set to local, load balancing still occurs before Traefik?