--- title: Configuring ingress cluster traffic by using a NodePort --- # Configuring ingress cluster traffic by using a NodePort {#configuring-ingress-cluster-traffic-nodeport} To enable external access to your application for specific networking requirements, expose a service by using a `NodePort`. This configuration opens a specific port on every node in the cluster, allowing external traffic to reach your workloads by using an IP address of any node. OpenShift Container Platform provides methods for communicating from outside the cluster with services running in the cluster. This method uses a `NodePort`. Before starting the following procedures, the administrator must complete the following prerequisite tasks: - Set up the external port to the cluster networking environment so that requests can reach the cluster. - Have an OpenShift Container Platform cluster with at least one control plane node, at least one compute node, and a system outside the cluster that has network access to the cluster. This procedure assumes that the external system is on the same subnet as the cluster. The additional networking required for external systems on a different subnet is out-of-scope for this topic. - Make sure there is at least one user with cluster admin role. To add this role to a user, run the following command: ``` $ oc adm policy add-cluster-role-to-user cluster-admin ``` ## Using a NodePort to get traffic into the cluster {#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport} 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` parameter > [!IMPORTANT] > Using a node port requires additional port resources. A `NodePort` exposes the service on a static port on the IP address of a node. A `NodePort` spans the `30000` to `32767` IP address ranges by default, which means a `NodePort` is unlikely to match the intended port of a service. For example, port `8080` might be exposed as port `31020` on the node. The administrator must ensure the external IP addresses are routed to the nodes. A `NodePort` and external IPs are independent and both can be used concurrently. ## Creating a project and service {#nw-creating-project-and-service_configuring-ingress-cluster-traffic-nodeport} If the project and service that you want to expose does not exist, create the project and then create the service. If the project and service already exists, skip to the procedure on exposing the service to create a route. **Prerequisites** - Install the OpenShift CLI (`oc`) and log in as a cluster administrator. **Procedure** 1. Create a new project for your service by running the `oc new-project` command: ```terminal $ oc new-project ``` 2. Use the `oc new-app` command to create your service: ```terminal $ oc new-app nodejs:12~https://github.com/sclorg/nodejs-ex.git ``` 3. To verify that the service was created, run the following command: ```terminal $ oc get svc -n ``` ```terminal {title="Example output"} NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nodejs-ex ClusterIP 172.30.197.157 8080/TCP 70s ``` > [!NOTE] > By default, the new service does not have an external IP address. ## Exposing the service by creating a route {#nw-exposing-service_configuring-ingress-cluster-traffic-nodeport} To enable external access to your application that runs on OpenShift Container Platform, you can expose the service as a route by using the `oc expose` command. **Prerequisites** - You logged into OpenShift Container Platform. **Procedure** 1. Log in to the project where the service you want to expose is located: ```terminal $ oc project ``` 2. To expose a node port for the application, modify the custom resource definition (CRD) of a service by entering the following command: ```terminal $ oc edit svc ``` ```yaml {title="Example output"} spec: ports: - name: 8443-tcp nodePort: 30327 port: 8443 protocol: TCP targetPort: 8443 sessionAffinity: None type: NodePort ``` - `nodePort`: Optional parameter. Specifies the node port range for the application. By default, OpenShift Container Platform selects an available port in the `30000-32767` range. - `type`: Specifies the service type. 3. Optional: To confirm the service is available with a node port exposed, enter the following command: ```terminal $ oc get svc -n myproject ``` ```terminal {title="Example output"} NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nodejs-ex ClusterIP 172.30.217.127 3306/TCP 9m44s nodejs-ex-ingress NodePort 172.30.107.72 3306:31345/TCP 39s ``` 4. Optional: To remove the service created automatically by the `oc new-app` command, enter the following command: ```terminal $ oc delete svc nodejs-ex ``` **Verification** - To check that the service node port is updated with a port in the `30000-32767` range, enter the following command: ```terminal $ oc get svc ``` In the following example output, the updated port is `30327`: ```terminal {title="Example output"} NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE httpd NodePort 172.xx.xx.xx 8443:30327/TCP 109s ``` **Additional resources** {._additional-resources} - [Configuring the node port service range](/openshift-docs-markdown/networking/configuring_network_settings/configuring-node-port-service-range#configuring-node-port-service-range) - [Adding a single NodePort service to an Ingress Controller](/openshift-docs-markdown/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy#nw-ingress-controller-nodeportservice-projects_nw-configuring-ingress-controller-endpoint-publishing-strategy)