How to access pod from outside of my cluster in kubernetes? I exposed it as node port service but can't access it with that node port

Question

I've created a pod for my java application and exposed it as a node-port service.
I'm able to access it using curl master address:nodeport only inside the cluster and not from the outside(say my browser).
The purpose of node-port service is to allow external access to pods right? then why can't access it.

kubernetes version v1.13,
Running in the digital ocean cloud.

Expected output: masteraddress:nodeport should work externally

output for kubectl describe svc <svc>

can share your Yaml file config ??? what is coming when you open 192.168.255.229:8081 ??? — Harsh Manvar, Feb 07 '19 at 11:52
@harsh config file of svc or pod?
I'm able to get the desired output when I open 192.168.255.229:8081 or nodeip:nodeport only inside my cluster — AATHITH RAJENDRAN, Feb 08 '19 at 04:00
ohhh okay...so with 192.168.255.229:8081 getting output ??? from browser or inside cluster ? — Harsh Manvar, Feb 08 '19 at 04:02
@HarshManvar digital ocean (p.s: I've mentioned that in my question) — AATHITH RAJENDRAN, Feb 08 '19 at 04:16
simply change nodeport type to load balancer digital ocean will make load balancer for you and you will get external IP..use it — Harsh Manvar, Feb 08 '19 at 04:17
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/188087/discussion-between-aathith-rajendran-and-harsh-manvar). — AATHITH RAJENDRAN, Feb 08 '19 at 04:18

score 0 · Answer 1 · edited Feb 07 '19 at 10:13

0

Check whether the node port is serving your application on host: netstat -tunpl | grep "your node port" and also with the Local Address as 0.0.0.0 or your machines' IP.

edited Feb 07 '19 at 10:13

PrakashG

1,642
5
20
30

answered Feb 07 '19 at 09:25

Vicky

121
5

yeah @vicky I checked and it worked fine using `localaddress:nodeport`, `masterip:nodeport`, and `netstat -tunpl | grep "my node port"` returns my node port – AATHITH RAJENDRAN Feb 08 '19 at 04:14

score 0 · Answer 2 · answered Feb 07 '19 at 09:29

0

Rather then using NodePort change it to load balancer and access it directly over load balancer Ip address. or eles you can make ingress controller which will make one ingress and you can redirect and exposes services

using ingress and service type load balancer both way you can you can acess application outside

answered Feb 07 '19 at 09:29

Harsh Manvar

27,020
6
48
102

from yaml file config also you can change config type:NodePort to LoadBalancer – Harsh Manvar Feb 07 '19 at 11:51

score 0 · Accepted Answer · answered Feb 08 '19 at 06:01

0

Just try and locate the worker node's IP address on which your pod is running.
change master-address:nodeport to workernode-address:nodeport, it worked for me :)

answered Feb 08 '19 at 06:01

AATHITH RAJENDRAN

4,689
8
34
58

score -1 · Answer 4 · answered Feb 07 '19 at 09:17

-1

If you are sure everything is correct and running,Check if port is blocked by firewall rules and open it for external traffic.

answered Feb 07 '19 at 09:17

Rajesh Deshpande

825
6
8

score -1 · Answer 5 · edited Feb 08 '19 at 20:21

-1

It looks from your output like your pod selector is not correct. Your output should be something like

Nodeport: "selector label" 31605/TCP

You have "unset", so this nodeport is not connected to anything.

I have a nodeport example on my blog.

edited Feb 08 '19 at 20:21

Cody Gray - on strike

239,200
50
490
574

answered Feb 08 '19 at 17:59

Jody Pearson

1

How to access pod from outside of my cluster in kubernetes? I exposed it as node port service but can't access it with that node port

5 Answers5