abundant-pharmacist-5287
10/09/2022, 11:17 AM$ kpodall [13:10:31]
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-b96499967-np7z8 1/1 Running 0 118s
kube-system local-path-provisioner-7b7dc8d6f5-5tf6p 1/1 Running 0 118s
kube-system helm-install-traefik-crd-vc5ff 0/1 Completed 0 119s
kube-system helm-install-traefik-7rt4l 0/1 Completed 1 119s
kube-system metrics-server-668d979685-2z7qx 1/1 Running 0 118s
kube-system traefik-7cd4fcff68-hr62c 1/1 Running 0 97s
kube-system svclb-traefik-e4c1ae56-6hbkx 0/2 CrashLoopBackOff 6 (48s ago) 97s
The traefik load balancer keeps on crashing. Is this known behavior for fedora 36?
In a previous cluster this ended with a message:
Warning FailedScheduling 50m (x18 over 136m) default-scheduler 0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Defaulted container "lb-tcp-80" out of: lb-tcp-80, lb-tcp-443
+ trap exit TERM INT
+ grep -Eq :
+ echo 10.43.46.110
+ cat /proc/sys/net/ipv4/ip_forward
+ '[' 1 '!=' 1 ]
+ iptables -t nat -I PREROUTING '!' -s 10.43.46.110/32 -p TCP --dport 80 -j DNAT --to 10.43.46.110:80
iptables v1.8.4 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
/etc/firewalld/firewalld.conf
sudo systemctl firewalld restart
and a restart of the cluster