Hello I'm facing an issue while setting cluster using aws instances. running a . . .

Kubernetes-Slack Discussions
#1

Hari:
Hello

I’m facing an issue while setting cluster using aws instances. running a 3 node cluster

The NodePort only responding on node where pod is running and not from outside and not from other nodes.

Name: nginx
Namespace: default
Labels: run=nginx
Annotations: <none>
Selector: run=nginx
Type: NodePort
IP: 10.100.76.103
Port: <unset> 80/TCP
TargetPort: 80/TCP
NodePort: <unset> 32593/TCP
Endpoints: 10.244.1.3:80,10.244.1.4:80,10.244.2.3:80 + 2 more…
Session Affinity: None
External Traffic Policy: Cluster
Events: <none>

kubectl get nodes
NAME STATUS ROLES AGE VERSION
ip-172-31-33-48 Ready master 73m v1.18.15
ip-172-31-35-107 Ready <none> 57m v1.18.15
ip-172-31-43-248 Ready <none> 61m v1.18.15

ubuntu@ip-172-31-35-107:~$ curl http://10.244.1.3:32593
curl: (7) Failed to connect to 10.244.1.3 port 32593: Connection timed out

#2

rlinux57:
kubect get nodes -o wide
get the external ip and curl with it.

#3

Hari:
ubuntu@ip-172-31-33-48:~$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-172-31-33-48 Ready master 130m v1.18.15 172.31.33.48 <none> Ubuntu 18.04.5 LTS 5.4.0-1055-aws docker://18.6.3
ip-172-31-35-107 Ready <none> 114m v1.18.15 172.31.35.107 <none> Ubuntu 18.04.5 LTS 5.4.0-1055-aws docker://18.6.3
ip-172-31-43-248 Ready <none> 118m v1.18.15 172.31.43.248 <none> Ubuntu 18.04.5 LTS 5.4.0-1055-aws docker://18.6.3