1

Even though internet connection is working properly, traceroute only shows node IP. Why?

Kubernetes version
1.21

enter image description here

Francisco Cardoso
  • 1,438
  • 15
  • 20
  • There is no requirement for any intermediate device respond to traceroute within the timeout or even respond at all. Traceroute is really only useful in your own network when you have knowledge of the correct path and have the routers configured to send ICMP TTL expired messages. – Ron Maupin Mar 08 '22 at 23:47

1 Answers1

2

Set -p 443 will result to host not to process the probe along the route. You can try kubectl run busybox --image busybox --restart Never -it --rm -- traceroute -4 -l -v -m 30 google.com. This command will show you the IP along the route; presumed your cluster has no network policy or subnet security group blocking the way.

gohm'c
  • 13,492
  • 1
  • 9
  • 16
  • 1
    You answer was very useful because I've found out that I didn't open all the required outbound ports for traceroute. When I tested with "all open" it worked perfectly. Now I just need to figure it out what ports are those. – Francisco Cardoso Mar 09 '22 at 10:24