LB crashloop

[AllardKrings]

Hi,

I have clean-installed K3S on my sbc running Ubuntu Mantic,

The K3s runs fine , traefik-pod runs fine, however the loadbalancers for port 80 and 443 crash with the message: ip-tables not found.

Maybe there is nothing wrong with ServiceLB but with my configuration. Any tips/suggestions?

kubectl get pod -A gives:

NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system local-path-provisioner-6d44f4f9d7-tl5bp 1/1 Running 0 6h40m
kube-system coredns-97b598894-8c5gh 1/1 Running 0 6h40m
kube-system metrics-server-7c55d89d5d-pv4kz 1/1 Running 0 6h40m
kube-system helm-install-traefik-crd-r8j7t 0/1 Completed 0 6h40m
kube-system helm-install-traefik-6pwvf 0/1 Completed 2 6h40m
kube-system traefik-8657d6b9f4-ctwtz 1/1 Running 0 6h37m
kube-system svclb-traefik-4ea49843-qhf9g 0/2 CrashLoopBackOff 164 (2m19s ago) 6h37m

kubectl logs svclb-traefik-4ea49843-qhf9g lb-tcp-80 -n kube-system gives:

• trap exit TERM INT
• BIN_DIR=/sbin
• check_iptables_mode
• set +e
• grep nf_tables
• lsmod
• '[' 1 '=' 0 ]
• mode=legacy
• set -e
  [INFO] legacy mode detected
• info 'legacy mode detected'
• echo '[INFO] ' 'legacy mode detected'
• set_legacy
• ln -sf /sbin/xtables-legacy-multi /sbin/iptables
• ln -sf /sbin/xtables-legacy-multi /sbin/iptables-save
• ln -sf /sbin/xtables-legacy-multi /sbin/iptables-restore
• ln -sf /sbin/xtables-legacy-multi /sbin/ip6tables
• start_proxy
• grep -Eq :
• echo 0.0.0.0/0
• iptables -t filter -I FORWARD -s 0.0.0.0/0 -p TCP --dport 80 -j ACCEPT
  /usr/bin/entry: line 46: iptables: not found

k3s —version gives:

k3s version v1.27.3+k3s-9d376dfb-dirty (9d376dfb)
go version go1.20.5

Ths SBC is a starfive visionvife 12a

Help appreciated!

KInd regards Allard Krings