You can not curl into cluster pods from outside the cluster whose service type i . . .

Kubernetes-Slack Discussions
#21

Hinodeya:
Edit the yaml and add nodePort: 30087

#22

Deepak Mourya:
I have used the service ip too, but it was not working . If we are using same cluster and same node then why cluster Ip is not working this is what my doubt

#23

Hinodeya:
after that retry curl command with the ip address of the node

#24

Hinodeya:
The current service just working for clusterIp

#25

Deepak Mourya:
Yes nodePort will but i want to test with the cluster IP

#26

Hinodeya:
So use the correct ip address of the node and check who is hosted the pods which node I mean

#27

Hinodeya:
curl -v for deeper informations also

#28

Hinodeya:
good luck

#29

Deepak Mourya:
@Hinodeya Thank you, i have checked these things but unfortunately session is not available right now. :neutral_face:

#30

Navratan Lal Gupta:
@Deepak Mourya as @Vinay pointed you can check if containerPort 8080 is exposed and add it using patch or edit command. U can bot donthat direct on pod I guess. You might need to redeploy new pod. Or if its controlled by object controller you can edit it