Node port
NodePort is a Kubernetes Service type that exposes a service through a designated port on every cluster node and routes traffic to its endpoints.
Kubernetes in Action, Second Edition
A NodePort Service is a Kubernetes Service type that exposes the service through a specified port on every cluster node as well as through its cluster IP.
- How it is used
- Exposes selected pods through a port on every cluster node when access through a cluster-only Service is insufficient.
- How deep it goes
- Works through manifest fields, port mappings, Service inspection, and cross-node forwarding without tracing packet-level implementation.
- Examples
- Demonstrates a two-port Service manifest, kubectl inspection, node-IP lookup, and a curl request to port 30080.
- What you can do after
- Build it from scratch with a Service manifest, then inspect its assigned ports and test access through a node IP.
Read how Kubernetes in Action, Second Edition explains node port →
Road to Kubernetes
A NodePort Service is a Kubernetes Service type that exposes a port on each cluster node and routes traffic to selected Pods.
- How it is used
- Exposes a Pod to external traffic quickly through a port on every cluster node.
- How deep it goes
- Defines NodePort and illustrates its Service YAML and cross-node routing, without detailing routing internals.
- Examples
- Uses an NGINX Service selecting app: my-nginx and forwarding node port 30007 to Pod port 80.
- What you can do after
- Apply it via Kubernetes Service YAML to expose selected Pods on a port available at every node.
Machine Learning Platform Engineering
A NodePort service is a Kubernetes service that exposes an application through a designated port on each cluster node.
- How it is used
- Exposes applications externally through cluster nodes when access is needed without a complex setup.
- How deep it goes
- Explains port roles, selectors, deployment commands, node discovery, external curl testing, and contrasts alternatives.
- Examples
- Demonstrates a hello-joker service, node IP discovery, kubectl inspection, and curl access on port 30420.
- What you can do after
- Operate/configure a NodePort service, apply its YAML, inspect nodes, and verify external connectivity with curl.
Read how Machine Learning Platform Engineering explains node port →
Google Anthos in Action
NodePort is a Kubernetes Service type that exposes a service through a port on each cluster node.
- How it is used
- Exposes Kubernetes Services to external resources and supports local application previews.
- How deep it goes
- Explains load-balancer, node, and Pod forwarding, then demonstrates creation, inspection, and local port forwarding.
- Examples
- Uses Anthos GKE hybrid networking and a minikube hello-minikube Deployment exposed on port 8080.
- What you can do after
- Operate/configure NodePort Services with kubectl and route external traffic through a load balancer or local port forwarding.
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
A Kubernetes Service type that exposes a service on a port of each cluster node for access from outside the cluster.
- How it is used
- Exposes locally deployed Kubernetes microservices through a node port for access from the host computer.
- How deep it goes
- Explains Service selection, port-range configuration, local testing, and troubleshooting, but defers deeper debugging.
- Examples
- Demonstrates video streaming at localhost:30000/video and gateway testing through an assigned local NodePort.
- What you can do after
- Operate/configure a NodePort Service, test it from a browser, and diagnose port mismatches with kubectl.
Acing the Certified Kubernetes Administrator Exam, Second Edition
A NodePort is a Kubernetes service type that exposes a service on a port of each cluster node.
- How it is used
- Exposes a Service for external traffic through a static port on every cluster node, especially for testing communication to Pods.
- How deep it goes
- Defines exposure, port range, commands, YAML changes, verification, and limitations without detailing networking internals.
- Examples
- Uses kubectl commands, port 30000, node address 100.96.95.252, and kubectl get svc output.
- What you can do after
- Apply it via kubectl, expose a Service on a chosen node port, and verify the resulting Service mapping.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains node port →
Related concepts
- servicekind of · A Kubernetes Service is an API resource that provides stable network access and service discovery for a changing set of Pods or other specified destinations.
- clusterip service typecontrasts with · ClusterIP is a Kubernetes Service type that exposes selected Pods through a stable virtual IP address accessible only within the cluster.
- load balancerused by · A load balancer is a hardware or software component that distributes incoming network traffic or requests among multiple destinations, such as servers or service instances.
- ingress objectalternative to · A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
- loadbalancer serviceproduced by · A Kubernetes LoadBalancer Service is a Service type that exposes workloads externally through a provisioned or integrated network load balancer.
- hostPortcontrasts with · The Kubernetes hostPort field exposes a container port through a corresponding network port on the node hosting the pod.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.