What is the url you are trying to hit? You should be okay if you’re using
host:nodeport . If that isn’t working you may want to check your firewall settings.
I was using the curl and the port is 80.
I did some research, I found this:
It seems related to the chain FORWARD rules are:
#iptables -L |grep FORWARD
Chain FORWARD (policy DROP)
KUBE-FORWARD all – anywhere anywhere /* kubernetes forwarding rules */
Chain KUBE-FORWARD (1 references)
BUT: after I run iptables -P FORWARD ACCEPT on all nodes and the master, the issue is still same.
Normally you would just use the ip of one of the nodes or the load balancer plus the node port the service is being exposed on and things should work good.
If you are trying to hit port 80 you’ll get a different behaviour.
I sorted out the issue. the issue is fixed after the ICMP is enabled in the security group.
Awesome, glad you figured it out!