Chapter 14. Configuring the node port service range

Prerequisites

• Installed the OpenShift CLI (oc).
• Logged in to the cluster as a user with cluster-admin privileges.
• You ensured that your cluster infrastructure allows access to the ports that exist in the extended range. For example, if you expand the node port range to 30000-32900, your firewall or packet filtering configuration must allow the inclusive port range of 30000-32900.

Procedure

• Expand the range for the serviceNodePortRange parameter in the network.config.openshift.io object that your cluster uses to manage traffic for pods by entering the following command in your command-line interface (CLI):

  $ oc patch network.config.openshift.io cluster --type=merge -p \
    '{
      "spec":
        { "serviceNodePortRange": "<port_range>" } 

  1

  
    }'

  Copy to Clipboard

  1

  Where <port_range> is your expanded range, such as 30000-32900.

  Tip

  You can also apply the following YAML to update the node port range:

  apiVersion: config.openshift.io/v1
  kind: Network
  metadata:
    name: cluster
  spec:
    serviceNodePortRange: "<port_range>"
  # ...

  Copy to Clipboard

  Example output

  network.config.openshift.io/cluster patched

  Copy to Clipboard

Verification

• To confirm a successful configuration, enter the following command. The update can take several minutes to apply.

  $ oc get configmaps -n openshift-kube-apiserver config \
    -o jsonpath="{.data['config\.yaml']}" | \
    grep -Eo '"service-node-port-range":["[[:digit:]]+-[[:digit:]]+"]'

  Copy to Clipboard

  Example output

  "service-node-port-range":["30000-32900"]

  Copy to Clipboard