mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 09:46:53 +01:00
26 lines
960 B
Plaintext
26 lines
960 B
Plaintext
// Module included in the following assemblies:
|
||
//
|
||
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc
|
||
|
||
[id="nw-using-nodeport_{context}"]
|
||
= Using a NodePort to get traffic into the cluster
|
||
|
||
Use a `NodePort`-type `Service` resource to expose a service on a specific port
|
||
on all nodes in the cluster. The port is specified in the `Service` resource's
|
||
`.spec.ports[*].nodePort` field.
|
||
|
||
[IMPORTANT]
|
||
====
|
||
Using ``NodePort``s requires additional port resources.
|
||
====
|
||
|
||
A `NodePort` exposes the service on a static port on the node's IP address.
|
||
``NodePort``s are in the `30000` to `32767` range by default, which means a
|
||
`NodePort` is unlikely to match a service’s intended port. For example, port
|
||
`8080` may be exposed as port `31020` on the node.
|
||
|
||
The administrator must ensure the external IP addresses are routed to the nodes.
|
||
|
||
``NodePort``s and external IPs are independent and both can be used
|
||
concurrently.
|