How do I externally access a service with kubernetes NodePort?

Question

I\'ve setup a NodePort service using the following config:

wordpress-service.yaml

apiVersion: v1
kind: Service
metadata:
  labels:
          


        

Answer 1

For Kubernetes on GCE:

We had the same question regarding services of type NodePort: How do we access node port services from our own host?

@ivan.sim 's answer (nodeIp:nodePort) is on mark however, you still wouldn't be able to access your service unless you add a firewall ingress (inbound to google cloud) traffic rule on the VPC network console to allow your host to be able to access your compute node

the above rule is dangerous and should be used only during development

You can find the node port using either the Google Cloud console or by running subsequent kubectl commands to find out the node running your pod which has your container. i.e kubectl get pods , kubectl describe pod your-pod-name, kubectl describe node node-that-runs-you-pod .status.addresses has your ExternalIP

It would be great if we could extract the node ip running our container in the pod using only a label/selector and a few line of commands, so here is what we did, in this case our selector is app: your-label:

$ nodename=$(kubectl get pods -o jsonpath='{.items[?(@.metadata.labels.app=="your-label")].spec.nodeName}')

$ nodeIp=$(kubectl get nodes -o jsonpath='{.items[?(@.metadata.name=="'$(echo $nodename)'")].status.addresses[?(@.type=="ExternalIP")].address}')

$ echo nodeIp

notice: we used json path to extract the information we desired, for more on json path see: json path

You could certainly turn this into a script that takes a label/selector as input and outputs an external ip of the node running your container !!!

To get the nodeport just type:

$ kubectl get services

under the PORT(S) columns you will see something like tagetPort:nodePort. this nodeport is what you want .

nodeIp:nodePort