Kubernetes - NodePort Service

Last Updated : 04 Jan, 2025

NodePort service in Kubernetes is a service that is used to expose the application to the internet from where the end-users can access it. If you create a NodePort Service Kubernetes will assign the port within the range of (30000-32767). The application can be accessed by end-users using the node's IP address.

Kubernetes Service

Kubernetes service will help you to expose the pods that are running in the cluster to the outside world and also they will make it available for the pods to each other that are running in the Kubernetes cluster.

Types Of Kubernetes Services

In Kubernetes, there are 3 types of services to provide discovery and routing between pods.

1. ClusterIP: It is the default service and its visibility is cluster internal which means it's not possible to use clusterIP service to reach a micro-service from the internet from outside the cluster.

2. NodePort: NodePort extends the ClusterIP service and its visibility is internal and external to the cluster. You can set a NodePort using the NodePort property, this is the port that the service will listen on from outside the cluster. There is one requirement of using NodePort which is nodes must have public IP addresses. The port must be in the range between 30000 and 32767 and if you don't specify the NodePort value Kubernetes will assign it randomly.

3. LoadBalancer: It operates at the transport level (TCP) that is at level 4. It means that is unable to make decisions based on content and it uses a simple algorithm such as a round-robin across the selected paths. Whereas Ingress operates at the application level which is at level 7. It is able to make decisions based on the actual content of each message. More intelligent load-balancing decisions and content optimizations. In other words, Ingress is like a LoadBalancer but more intelligent.

For our article, we'll use NodePort service for service discovery.

Kubernetes NodePort Service

Kubernetes NodePort Service is an service which is used for to expose the nodes which are available in the cluster to the outside of the cluster. It will also expose the applications which are running in the node it also allows the traffic from the outside to reach the application with the help of NodePort.

Example Of NodePort Service

Following is the sample YAML file for the kubernetes NodePort Service.

apiVersion: v1
kind: Service
metadata:
  name: <Name Of the Service> 
spec:
  type: NodePort
  ports:
  - port: 80          # Port exposed within the cluster
    targetPort: 8080  # Port on the pods
    nodePort: 30000   # Port accessible externally on each node
  selector:
    app: example-app  # Select pods with this label

How NodePort Service Work?

NodePort service will exposes the pods of node to the another and also it will expose the pods to the outside of the cluster from where the users can aceses from the internet by using the IP address of node and port.

Following is the sample YAML file for NodePort Service.

apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
selector:
app: my-app
type: NodePort
ports:
- protocol: TCP
port: 80
targetPort: 80

APIversion of the service is V1 and the kind was service there are two important things to consider here first one is above YAML file you can see port 80 and targetPort 80 the major difference between this two was Port on which port does service expose the pod outside and the target port is the port where pod listens.

Steps To Use NodePort Service

Step 1. Create a deployment. For our demo purpose, I choose Nginx as our application with 2 replicas, you can change it as per your requirement.

$ kubectl create deploy 
--image=nginx:1.23 nginx 
--replicas=2

Step 2. Expose service with NodePort

kubectl expose deploy nginx 
--type=NodePort --port=8080 
-target-port=80

we exposed our deployment as a NodePort service with the name nginx-service

Check your service (Optional):

$ kubectl get svc nginx
-service -o wide

You can see we've successfully exposed our service with NodePort

Step 3. Access your application

$ minikube service 
nginx-service --url

On invoking this, you can see it in the browser:

As you can see in the above image we can access our application on our machine which is running on our cluster, this is only possible because of the NodePort service.

Difference Between NodePort And ClusterIP

NodePort	ClusterIP
NodePort service will exposes the static port on each IP address and also it allows the traffic from internet to access the pod.	Expose the service on an internal IP address which can be reachable with in the cluster.
If you want to expose the pods to external and also want to use it for inside the cluster then you can use NodePort.	If you didn't want to expose the pod to out side and need to be used for internal purpose you can use the ClusterIP.
If you need to expose the application like web-applications then you can use the NodePort Serivce	Mainly used for the internal purposes like databases API services which are used for internal purpose.

NodePort service is used to expose the application outside of the cluster and ClusterIP is used to access for internal purpose only.

Kubernetes - ClusterIP vs NodePort vs LoadBalancer

anuragsinghrajawat22

Improve

Article Tags :

Kubernetes - NodePort Service

Kubernetes Service

Types Of Kubernetes Services

Kubernetes NodePort Service

Example Of NodePort Service

How NodePort Service Work?

Steps To Use NodePort Service

Difference Between NodePort And ClusterIP

Similar Reads

Introduction to Kubernetes

Installation and Setup

Application Deployment

Configmaps

Scaling and Updating Applications

Additional Topics