Welcome to the Linux Foundation Forum!

ClusterIP accessible only from the node where the POD is running

I created a basic pod and basic service.
ubuntu@ip-172-31-41-74:~/mySamples$ kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
basicservice ClusterIP 10.96.191.90 80/TCP 27m
kubernetes ClusterIP 10.96.0.1 443/TCP 21h

But if I run "curl http://10.96.191.90", it works only on the node that runs the backend pod. Checked iptables and looks like kube_proxy hasn't created a iptable rule for this cluster IP. Any idea how to fix it?

Comments

  • Posts: 1,000

    Hello,

    Are you sure that you have opened the AWS firewall so that all traffic is allowed between nodes?

    Regards,

  • Hi,
    This type of issue is seen when the SG is too restrictive on AWS. As @serewicz noted, make sure that SG is open to all traffic to allow nodes to talk to each other.

    Regards,
    -Chris

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training