Closed CasparChou closed 5 years ago
maybe iptables issue
I have been reset iptables and restart svclb-traefik daemonSet, still no route to 10.43.0.0/16
svclb-traefik
k3s v0.7.0 (v1.14.4-k3s.1) traefik (1.7.9) coredns (1.3.1) worker os (ubuntu 16.04.5 desktop amd64) master os (ubuntu 18.04 server amd64) worker environment: edge, behind nat, floating ip (4G LTE) master environment: aws ec2, public subnet
maybe iptables issue
I have been reset iptables and restart
svclb-traefikdaemonSet, still no route to 10.43.0.0/16k3s v0.7.0 (v1.14.4-k3s.1) traefik (1.7.9) coredns (1.3.1) worker os (ubuntu 16.04.5 desktop amd64) master os (ubuntu 18.04 server amd64) worker environment: edge, behind nat, floating ip (4G LTE) master environment: aws ec2, public subnet