This message was deleted Rancher Users #k3s

Join Slack

This message was deleted.

# k3s

adamant-kite-43734

06/27/2025, 6:27 AM

This message was deleted.

rich-dream-58859

06/27/2025, 4:05 PM

Did you happen to find a solution to this? It looks like I am having the same, or very similar issue.

rich-dream-58859

06/27/2025, 4:37 PM

Just to compare notes a little... I am seeing in on the node:

Copy code

cat /run/flannel/subnet.env
FLANNEL_NETWORK=10.42.0.0/16
FLANNEL_SUBNET=10.42.2.1/24
FLANNEL_MTU=1450
FLANNEL_IPMASQ=true

and a pod running on the node:

Copy code

cat /etc/resolv.conf
search mynamespace.svc.cluster.local svc.cluster.local cluster.local
nameserver 10.43.0.10
options ndots:5

rich-dream-58859

06/27/2025, 4:37 PM

but the address

10.43.0.10

doesn't seem to be assigned/allocated to anything

rich-dream-58859

06/27/2025, 4:42 PM

I do have an iptables rule on the node, but I am not sure why.

Copy code

iptables -L | grep 10.43
RETURN     all  --  anywhere             10.43.0.0/16         /* allow traffic to primary/secondary cluster IP range - EKROEGTNIJ3AP3LC */
REJECT     tcp  --  anywhere             10.43.168.0          /* default/nginx has no endpoints */ tcp dpt:http reject-with icmp-port-unreachable

72 Views

Open in Slack

Previous Next