Kubernetes NodePort: How to expose services externally

A NodePort Service exposes your application on a port between 30000 and 32767 on every node in the cluster. External traffic arriving at any node's IP address on that port is routed through to the correct pods via the Service's selector.

NodePort is the simplest way to expose a Kubernetes Service to traffic from outside the cluster without requiring a cloud load balancer.

When to use NodePort

NodePort is appropriate when:

• You are running on bare metal or on-premises infrastructure where no cloud load balancer is available
• You are in a development or testing environment and need quick external access
• You are building a custom ingress or load balancing solution on top of NodePort and want to manage the external routing yourself
• You need a predictable, stable port that an external system can connect to

For production workloads on cloud infrastructure, LoadBalancer is usually the better choice as it provisions an external IP automatically without requiring you to manage node IPs or firewall rules.

How NodePort traffic flows

When external traffic arrives at <NodeIP>:<NodePort>:

1. The node receives the traffic on the NodePort
2. The Service routes it to the ClusterIP
3. The ClusterIP load-balances it across the healthy pods matching the Service's selector
4. The selected pod receives the request

Every node in the cluster listens on the NodePort, so you can use any node's IP address to reach the Service. If one node is unavailable, the others still serve traffic on the same port.

Working example

Create a namespace and a deployment:

1kubectl create namespace example
2kubectl create deployment demo --image=nginx --port=3000 -n example

Create a NodePort Service:

1apiVersion: v1
2kind: Service
3metadata:
4  name: demo-nodeport
5  namespace: example
6spec:
7  type: NodePort
8  selector:
9    app: demo
10  ports:
11  - port: 80
12    targetPort: 3000
13    nodePort: 31520

1kubectl apply -f nodeport.yaml

Verify the Service was created:

1kubectl get all -n example

Expected output:

1NAME                        READY   STATUS    RESTARTS   AGE
2pod/demo-6b7f9d8c5-abc12    1/1     Running   0          30s
3
4NAME                   TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
5service/demo-nodeport  NodePort   10.96.145.23    <none>        80:31520/TCP   10s

The Service is now accessible at <NodeIP>:31520 from outside the cluster.

NodePort range and automatic assignment

NodePort values must be in the range 30000 to 32767. If you omit the nodePort field from the Service spec, Kubernetes assigns an available port automatically from within this range.

Manually specifying a port as in the example above is useful when you need a predictable, stable port for external load balancer configuration or when you want consistent port numbers across environments.

Comparison: NodePort vs LoadBalancer

Use NodePort when you need external access without a cloud load balancer. Use LoadBalancer when you want the cloud provider to provision an external IP automatically.